Skip to content

Publish to NPM registry. #71

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

pauldruce
Copy link

@pauldruce pauldruce commented Feb 4, 2025

Summary of changes:

  • I've added a github workflow which will publish this project as a package on npmjs and the github npm registry.
    • This is essentially the same process that bats-core is using to publish as a node package.
    • This requires a secret called NPM_TOKEN for the existing project to work for the npmjs registry.
    • Publishing to the GitHub npm registry should work without any extra secrets.
  • Listed bats and bats-support as actual dependencies, as bats-assert isn't much use without them.
  • A smoke test of the npm installation was added to show it works.

This PR addressing #70

@pauldruce
Copy link
Author

From looking at the current npmjs project. I expect that @jasonkarns should take a look at this, as in order to successfully publish to npmjs, we need an access token for the project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant