When we publish to npmjs.com, there seems to be a background process which exec's npm install && npm run build. It also appears to autoincrement the version (currently 1.0.5, rather than our code's 1.0.4).
We've also published a LICENSE file here as aGPL, but the npmjs.com repo does not list a license.
Identify best practices for the npmjs,com publishing:
- How do we keep the versions in-sync?
- How do we expose the license?
- How do connect the ULS with the management of the npmjs.com distribution?
When we publish to npmjs.com, there seems to be a background process which exec's
npm install && npm run build. It also appears to autoincrement the version (currently 1.0.5, rather than our code's 1.0.4).We've also published a LICENSE file here as aGPL, but the npmjs.com repo does not list a license.
Identify best practices for the npmjs,com publishing: