05f55c1c30
Closes: CNVS-35152 This changes all our tooling that used `npm` to Run scripts to use `yarn`. `npm` will still work for now but if you have yarn installed, it will use that. Cheat Sheet: old command -> new command npm install -> yarn install (or just `yarn`) npm run webpack -> yarn run webpack npm test -> yarn test See more at https://yarnpkg.com Test plan: * all Jenkins builds should pass * without yarn installed: * run script/nuke_node.sh * it should work and warn you about how `npm` is deprecated * now install yarn, e.g.: `brew install yarn` * run script/nuke_node.sh again * it should work and you should see silly yarn emoji in the output and it should be a lot faster * the docker changes I made should work and docker should build correctly and use yarn. Change-Id: I4aa31eeae3ecc504634a7c72a1ea0d3396f445e3 Reviewed-on: https://gerrit.instructure.com/102969 Tested-by: Jenkins Reviewed-by: Brent Burgoyne <bburgoyne@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> |
||
|---|---|---|
| .. | ||
| bin | ||
| lib | ||
| spec/selinimum | ||
| Gemfile | ||
| package.json | ||
| selinimum.gemspec | ||
| test.sh | ||
| yarn.lock | ||