Skip to content

Commit 53bfe3f

Browse files
nickservmihar-22
authored andcommitted
chore: use npm instead of yarn
1 parent d63da1c commit 53bfe3f

File tree

3 files changed

+17
-31
lines changed

3 files changed

+17
-31
lines changed

.travis.yml

+7-17
Original file line numberDiff line numberDiff line change
@@ -1,29 +1,19 @@
11
sudo: false
22
language: node_js
3-
cache:
4-
yarn: true
5-
directories:
6-
- "~/.npm"
73
notifications:
84
email: false
95
node_js:
106
- '10'
117
- '12'
128
- '14'
13-
env:
14-
global:
15-
- PATH=$HOME/.yarn/bin:$PATH
16-
before_install:
17-
- curl -o- -L https://yarnpkg.com/install.sh | bash
18-
install: yarn
19-
script: yarn validate
9+
script: npm run validate
2010
jobs:
2111
include:
22-
- stage: release
23-
node_js: '14'
24-
deploy:
25-
provider: script
26-
script: yarn test:update && npx codecov && npx semantic-release
27-
skip_cleanup: true
12+
- stage: release
13+
node_js: '14'
14+
deploy:
15+
provider: script
16+
script: npm run test:update && npx codecov && npx semantic-release
17+
skip_cleanup: true
2818
branches:
2919
only: master

CONTRIBUTING.md

+2-6
Original file line numberDiff line numberDiff line change
@@ -7,12 +7,8 @@ to an Open Source Project on GitHub][egghead]
77

88
## Project setup
99

10-
Make sure that Yarn is installed.
11-
<br>
12-
Installation instructions can be found here: https://yarnpkg.com/en/docs/install.
13-
1410
1. Fork and clone the repo
15-
2. Run `yarn setup` to install dependencies and run validation
11+
2. Run `npm run setup -s` to install dependencies and run validation
1612
3. Create a branch for your PR with `git checkout -b pr/your-branch-name`
1713

1814
> Tip: Keep your `master` branch pointing at the original repository and make pull requests from
@@ -32,7 +28,7 @@ Installation instructions can be found here: https://yarnpkg.com/en/docs/install
3228
3329
## Committing and Pushing changes
3430
35-
Please make sure to run the tests before you commit your changes. You can run `yarn test:update`
31+
Please make sure to run the tests before you commit your changes. You can run `npm run test:update`
3632
which will update any snapshots that need updating. Make sure to include those changes (if they
3733
exist) in your commit.
3834

package.json

+8-8
Original file line numberDiff line numberDiff line change
@@ -41,10 +41,10 @@
4141
"clean": "rimraf dist",
4242
"build": " babel src --out-dir dist --ignore '**/__tests__/**,**/__mocks__/**'",
4343
"test": "jest src/__tests__ ",
44-
"test:watch": "yarn test --watch",
45-
"test:update": "yarn test --updateSnapshot --coverage",
46-
"setup": "yarn && yarn validate",
47-
"validate": "yarn lint && yarn test && yarn clean && yarn build",
44+
"test:watch": "npm test --watch",
45+
"test:update": "npm test --updateSnapshot --coverage",
46+
"setup": "npm install && npm run validate",
47+
"validate": "npm run lint && npm test && npm run clean && npm run build",
4848
"contributors:add": "all-contributors add",
4949
"contributors:generate": "all-contributors generate"
5050
},
@@ -94,17 +94,17 @@
9494
},
9595
"lint-staged": {
9696
"README.md": [
97-
"yarn toc",
97+
"npm run toc",
9898
"prettier --parser markdown --write",
9999
"git add"
100100
],
101101
".all-contributorsrc": [
102-
"yarn contributors:generate",
102+
"npm run contributors:generate",
103103
"git add"
104104
],
105105
"**/*.js": [
106-
"yarn lint",
107-
"yarn test",
106+
"npm run lint",
107+
"npm test",
108108
"git add"
109109
]
110110
},

0 commit comments

Comments
 (0)