Skip to content

Commit

Permalink
Replace npm usage with yarn (#782)
Browse files Browse the repository at this point in the history
  • Loading branch information
ozelot379 authored and hipstersmoothie committed Sep 2, 2019
1 parent 7dff287 commit 0a64631
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ If you know how to code, we welcome you to send fixes and new features, but in o
- Code your changes (if you want to implement many features do each one in a separated branch);
- Write tests to ensure your feature works as expected and protect its behavior on future changes;
- Test it! Ensure you don't crash Jimp in Node.js or Browser environments;
- Full test with `npm test` will also produce a coverage report.
- Full test with `yarn test` will also produce a coverage report.
- For more option, see the "[Testing](#testing)" topic bellow.
- Push to your forked repo;
- Make your pull request.
Expand All @@ -38,7 +38,7 @@ yarn build:watch # build ES5 version in watch mode. Good to run while testing or

### Testing

The test framework runs at Node.js and browsers environments. Just run `npm test` to test in node and browser environments.
The test framework runs at Node.js and browsers environments. Just run `yarn test` to test in node and browser environments.
You can use the coverage report to help with missed tests, but you must be aware: it only shows if a line of code was evaluated while testing, not if all relevant test cases was done to protect the feature behavior.

While developing you may want to test only on node.js:
Expand All @@ -65,7 +65,7 @@ yarn test:watch
yarn run test:browser -- --browsers Firefox
```

For more options and project management tools see: `npm run`
For more options and project management tools see: `yarn run`

## Collaborators are Welcome

Expand Down

0 comments on commit 0a64631

Please sign in to comment.