-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
47 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
# Pubishing | ||
|
||
## Setup to publish in NPM | ||
|
||
In command line: | ||
|
||
```bash | ||
npm adduser | ||
``` | ||
|
||
## Publish in NPM | ||
|
||
In command line: | ||
|
||
```bash | ||
npm version x.y.z | ||
npm version [major | minor | patch] | ||
npm version x.y.z --no-git-tag-version # use this if release is created in github first | ||
``` | ||
|
||
For example, to release a patch version: | ||
|
||
```bash | ||
npm version patch -m "(dev): tag %s" | ||
npm publish --access public | ||
``` | ||
|
||
These commands will create a tag in git, so push to repo after them. | ||
|
||
Also, create a release in the repo after all. | ||
|
||
## Deprecate package | ||
|
||
In command line: | ||
|
||
```bash | ||
npm deprecate <package-name>@<version> "<message>" | ||
``` |