You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not familiar with how publishing to npm works exactly, but from https://docs.github.com/en/actions/publishing-packages/publishing-nodejs-packages it seems to be possible to use a GitHub action workflow to publish to npm after a new release was created (the example workflow listed in the docs seems relatively straightforward and only requires the npm Api token to be configured as secret (here in the GitHub repository)
This would ensure the latest build is automatically also available on npm (e.g. currently npm is on 3.3.40 - and latest master here is already on 3.3.43
The text was updated successfully, but these errors were encountered:
I'm not familiar with how publishing to npm works exactly, but from https://docs.github.com/en/actions/publishing-packages/publishing-nodejs-packages it seems to be possible to use a GitHub action workflow to publish to npm after a new release was created (the example workflow listed in the docs seems relatively straightforward and only requires the npm Api token to be configured as secret (here in the GitHub repository)
This would ensure the latest build is automatically also available on npm (e.g. currently npm is on 3.3.40 - and latest master here is already on 3.3.43
The text was updated successfully, but these errors were encountered: