We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Hello,
I forked the project to upload #514. Now, until #514 is merged upstream, I want to release my fork with the fix.
Usually there is a single package.json. Here there are many of them and they are not orchestrated by a lerna like tool.
package.json
lerna
What are the steps allowing to release (i.e. build and push artifacts to npmjs & cie) the project?
The text was updated successfully, but these errors were encountered:
Here is the script that worked for me:
#!/bin/bash set -xe npm run unlink npm version prerelease --preid=alpha4cosium --git-tag-version=false --prefix tool npm version prerelease --preid=alpha4cosium --git-tag-version=false --prefix target/src git add . npm version prerelease --preid=alpha4cosium --force npm ci npm test npm run pack-tool npm run pack-runtime npm publish ./tool npm publish ./target/src
Sorry, something went wrong.
No branches or pull requests
Hello,
I forked the project to upload #514. Now, until #514 is merged upstream, I want to release my fork with the fix.
Usually there is a single
package.json
. Here there are many of them and they are not orchestrated by alerna
like tool.What are the steps allowing to release (i.e. build and push artifacts to npmjs & cie) the project?
The text was updated successfully, but these errors were encountered: