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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,12 +120,14 @@ You can take a look at the milestones list to know in what milestone we are work
120
120
121
121
## How to publish a new version in npm
122
122
123
-
1.Logging into npm (be part of michelada organization in npm)
123
+
1.Log into npm (be part of michelada organization in npm)
124
124
2. Update the version number in package.json
125
125
- You can do it manually, updating the version number in the package.json.
126
126
- Or using the command `npm --no-git-tag-version version <update_type|number>` in the folder terminal. https://docs.npmjs.com/cli/v7/commands/npm-version
127
127
- The "version" field must be in the form x.x.x and follow the semantic-versioning guidelines. https://docs.npmjs.com/about-semantic-versioning
128
-
3. Run the command `npm publish --access public`
129
-
4. Verify in npm if the new version and the package is updated.
130
-
**_ Do not forget to push your changes _**
131
-
[]
128
+
3. Run the following commands in order:
129
+
*`npm run build`
130
+
*`npm run pre-publish`
131
+
*`npm run post-pre-publish`
132
+
*`npm run upload`
133
+
4. Verify in npm if the new version and the package is updated. **_Do not forget to push your changes_**
0 commit comments