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
Was this helpful?
Last updated
Was this helpful?
This page is part of list - 3/7
The is typically the go-to spot for uploading 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.
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.
But, with being an project, I got curious about leveraging GitHub's package navigation section:
Turns out, to get your packages listed there, you’ve got to use .
If you are not up to date - there is a new kid on the block when it comes to registries: (JavaScript Registry by Deno)
