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
To make our lives easier, we don't release that often but when we do usually getting interrupted because of some obscure fact that we need to run npm run all twice (once as part of the release command) is something that we should improve.
The text was updated successfully, but these errors were encountered:
Update the Release Script: Modify the package.json file to include a more robust release command that handles all required tasks in one go. For example:
"scripts": {
"all": "npm run lint && npm run build && npm run test",
"release": "npm run all && npm publish"
}
In this case, you’ll only need to run npm run release, which internally runs npm run all and handles the full release process, including publishing.
Check Existing Processes: Ensure all necessary steps (e.g., linting, testing, building) are included within npm run all or the release command. This avoids missing anything critical during the release.
What should we do
Make the release command consistent
Why should we do it
To make our lives easier, we don't release that often but when we do usually getting interrupted because of some obscure fact that we need to run
npm run all
twice (once as part of the release command) is something that we should improve.The text was updated successfully, but these errors were encountered: