...
- If you're not familiar with how to package a JS module and and share it on NPM, get your bearings by reading their docs.
- Modify your repo's Travis configuration so that tagging a release results in a publish to npmjs.
Contact Create a DevOps Support ticket to have DevOps get publish tokens for the edX NPMJS account . Use and have DevOps add it to the travis config using the Travis CI command line client to encrypt the token:
Code Block language bash travis encrypt --add deploy.api_key NPMTOKEN
- There are two options here
- using the Stages feature of Travis (studio-frontend)
- using Travis' simple built-in deploy
- Pitfalls: If prefixing your package name with the
@edx
package scope (which you should!) you'll need to make sure you specify to npm that you still want the package to be public by doing this.
- Pitfalls: If prefixing your package name with the
- Travis documentation on NPM deployment
- To publish a new version of your package, update the version, then push a corresponding tag to GitHub. You can do this using
npm version a.b.c
and it will update the version and tags for you - You're done! Don't forget to update webpack files so they download the new package from NPM.
...