Publishing Packages
The vis project contains multiple packages, each of which is published to the Allen Institute NPM organization package registry.
Publishing a New Package
Section titled “Publishing a New Package”When you have a new package to publish, follow these steps to publish it:
-
Authenticate with NPM by running
npm loginin your terminal and entering your credentials. Make sure the account you’re used is part of the Allen Institute NPM organization. -
Add the necessary information about the repository and the registry to the
package.jsonfile:
"repository": { "type": "git", "url": "https://github.com/AllenInstitute/vis.git" }, "publishConfig": { "registry": "https://registry.npmjs.org", "access": "public" },-
Run
pnpm publishin the package directory. -
Verify your package is available. You can see it listed on the Allen Institute’s NPM organization package registry or on the homepage of this repository.
Updating an Existing Package
Section titled “Updating an Existing Package”When you have changes to an existing package that you want to publish, follow these steps to publish the changes:
-
Authenticate with NPM by running
npm loginin your terminal and entering your credentials. Make sure the account you’re used is part of the Allen Institute NPM organization. -
Update the version number in the
package.jsonfile, following the Semantic Versioning standard. -
Get that version number update onto the
mainbranch and make sure everything is ship-shape for publishing. -
Run
pnpm publishin the package directory. -
Verify that the updated package is available. You can see it listed on the Allen Institute’s NPM organization package registry or on the homepage of this repository.
Troubleshooting
Section titled “Troubleshooting”If any of the previous steps don’t work due to updates in GitHub’s platform, please reference GitHub’s documentation for details and submit a PR updating this documentation.