3. Module registry (a place where packages get to chill)
Previous2. A module bundler - the fun beginsNext4. Versioning, Publishing, and Configuring lerna.json for Commit Conventions
Last updated
Last updated
This page is part of list - 3/7
The NPM registry is typically the go-to spot for uploading packages.
But, with exile.watch being an open-source project, I got curious about leveraging GitHub's package navigation section:
Turns out, to get your packages listed there, you’ve got to use GitHub Packages.
So, I decided to dive into the GitHub Packages NPM registry.
This move wasn’t just about getting our packages neatly listed; it was also a chance to really see what it's like to work with GitHub Packages.
And honestly, this experience could fill another blog post, which I might just write up someday.
If you are not up to date - there is a new kid on the block when it comes to registries: JSR (JavaScript Registry by Deno)
Moving forward, we'll explore how Lerna aids in module versioning and publishing, and how tweaking lerna.json helps enforce commit conventions in our project.
