@proprioo/salatim 37.0.0 → 37.0.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  Salatim is our component library, made with 🥑 and ❤️.
4
4
 
5
- Please have a look on its storybook for each components.
5
+ Please have a look at its storybook for each component.
6
6
 
7
7
  ## How to dev ?
8
8
 
@@ -13,17 +13,17 @@ Please have a look on its storybook for each components.
13
13
 
14
14
  ## How to release a new version?
15
15
 
16
- Final "production" release of salatim are managed through npmjs.com -- https://www.npmjs.com/package/@proprioo/salatim
16
+ The final "production" release of salatim is managed through npmjs.com https://www.npmjs.com/package/@proprioo/salatim
17
17
 
18
18
  To publish a new version of salatim, you need to:
19
19
 
20
20
  - checkout the `main` branch
21
21
  - make sure everything is up to date with `git pull origin main`
22
22
  - [optional by now] update the `CHANGELOG.md` file according to the changes you made since the last release
23
- - create either a **patch**, **minor** or **major** release depending on the changes you made using yarn
24
- - i.e. `yarn version --patch` for a patch release
25
- - i.e. `yarn version --minor` for a minor release
26
- - i.e. `yarn version --major` for a major release
23
+ - create either a **patch**, **minor** or **major** release depending on the changes you made using npm
24
+ - i.e. `npm version patch` for a patch release
25
+ - i.e. `npm version minor` for a minor release
26
+ - i.e. `npm version major` for a major release
27
27
  - push the commit and the tag created by the previous command using `git push origin main --tags`
28
28
  - go to GitHub and create a new release from the tag you just pushed
29
29
 
@@ -38,8 +38,8 @@ If you have to backport something to an old version of salatim :
38
38
  2. add your commit(s), and don't forget to bump the version in `package.json` and `CHANGELOG.md` (if you fix something
39
39
  and the previous version was `15.2.3`, bump to `15.2.4`)
40
40
  3. push the branch, don't forget it!
41
- 4. run `yarn clean && yarn build` locally to make the package ready to be published
42
- 5. run `yarn publish --access=public --non-interactive --tag 15.2.4` locally. **Don't forget the `--tag` argument to
41
+ 4. run `npm run clean && npm run build` locally to make the package ready to be published
42
+ 5. run `npm publish --access=public --non-interactive --tag 15.2.4` locally. **Don't forget the `--tag` argument to
43
43
  prevent overriding the latest version.**
44
44
 
45
45
  You can then bump your project with this new version of salatim. ;)