graphprotocol / graphprotocol/indexer
Feature request: Testing for NPM package publishing
Open
@fordN is already working on this.
Since Apr 21, 2022.
hardening
p3
- Dominant language
- TypeScript
- Stars
- 262
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
In order to ensure NPM packages build successfully for our users in different environments let's get in the habit of testing package publishing with each PR merge.
A few options:
- Use a local, private registry built with Verdaccio (or similar) to test package publishing locally.
- Setup a hosted registry using Verdaccio (or similar) which is automatically published to with every PR merge. This approach would provide a publicly accessible registry with all canary builds that indexers can test.
- Use a similar approach to previous but deploy to the official NPM registry using
alphaorcanarytags.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.