Publishing a JavaScript library for public use requires some extra steps. You need to think about how people will use the library. From end users, to contributors your library now has a variety of people outside of yourself potentially making use of the code that you've released into the wild.
From Github and npm, to releasing beta versions, semantic versioning, code coverage, continuous integration, and providing your library with a solid set of unit tests, there are a ton of things to learn.
This series will guide you through a set of steps to publish a JavaScript open source library.
You might also enjoy this article about contributing to open source.
From Github and npm, to releasing beta versions, semantic versioning, code coverage, continuous integration, and providing your library with a solid set of unit tests, there are a ton of things to learn.
This series will guide you through a set of steps to publish a JavaScript open source library.
You might also enjoy this article about contributing to open source.
