ff-stream-web

git clone git://archive.git.mtrnord.blog/MTRNord/ff-stream-web.git
Log | Files | Refs | README | LICENSE

commit 97fbda638a719bda3842ca313c909112af1b6b9f
parent d33639365cc5374e89087c7d02f7d76fdd1e4446
Author: Bryan Jensen <bryanawjensen@gmail.com>
Date:   Mon,  2 Jan 2017 00:29:10 -0800

Change references to npm to reference yarn instead (#1060)


Diffstat:
MCONTRIBUTING.md | 4++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md @@ -48,13 +48,13 @@ forked repo, check that it meets these guidelines: * Create a separate PR for each small feature or bug fix. * [Squash](http://stackoverflow.com/questions/5189560/squash-my-last-x-commits-together-using-git) your commits into one for each PR. -* Run `npm test` to make sure that your code style is OK and there are no any regression bugs. +* Run `yarn test` to make sure that your code style is OK and there are no any regression bugs. * When contributing to an opt-in feature, apply the `[feature/...]` tag as a prefix to your PR title #### Style Guide Our linter will catch most styling issues that may exist in your code. You can check the status -of your code styling by simply running: `npm run lint` +of your code styling by simply running: `yarn lint` However, there are still some styles that the linter cannot pick up. If you are unsure about something, looking at [Airbnb's Style Guide](https://github.com/airbnb/javascript) will guide you