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
Standard practice with node.js modules is to commit all of the changes for a release except updating the package.json version, and then run the following:
4
+
5
+
```
6
+
npm version major|minor|patch
7
+
git push --tags
8
+
git push origin master
9
+
npm publish
10
+
```
11
+
12
+
`npm version *` will update the package.json version field appropriately and create a git commit and tag for the version.
13
+
`git push --tags` will publish the tag to github., and then immediately.
14
+
`git push origin master` will publish the changes to package.json.
15
+
`npm publish` will publish the npm package.
16
+
17
+
The reason for this is that it allows someone to easily view the source code (and readme) for whatever version they happen to have downloaded from npm. This is particularly helpful when github is ahead of npm.
0 commit comments