chore(README):fix README.md

neeboo/contract
neeboo 5 years ago
parent 9dc33eca47
commit 0ff928bc62
  1. 45
      README.md

@ -267,20 +267,51 @@ yarn build && yarn test:e2e
The packages is to be published to npm, using `@next` tag using script in `package.json` The packages is to be published to npm, using `@next` tag using script in `package.json`
Follow steps below to publish a npm verion using `@next` tag
1. Commit all changes to github master 1. Commit all changes to github master
2. Run publish script 2. Run publish script
```bash
yarn dev:publish ```bash
``` yarn dev:publish
3. Confirm all prompt with `Y` ```
3. Select version and confirm all prompts with `Y`
4. See version changes in `npmjs.com` 4. See version changes in `npmjs.com`
This will not change the release version of current npm packages(currently 0.0.7), developers have to use `@next` to install from npm.
For example.
```bash
npm install @harmony-js/core@next
```
## Publish to npm with `lerna` ## Publish to npm with `lerna`
Follow steps below to publish a npm verion with latest version
1. Commit all changes to github master 1. Commit all changes to github master
2. Run `lerna publish`, `lerna` is required globally. 2. Run `lerna publish`, `lerna` is required globally.
```bash
lerna publish ```bash
``` lerna publish
```
3. Select version and confirm all prompts with `Y`
4. See version changes in `npmjs.com`
This will change the release version of current npm packages to the latest version, developers can install from npm directly
For example.
```bash
npm install @harmony-js/core
```

Loading…
Cancel
Save