2 Commits

Author	SHA1	Message	Date
Ryan Shaw	05f55c1c30	Deprecate `npm` client. Use `yarn` instead ... 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>	2017-03-01 19:39:01 +00:00
Nathan Mills	25154ed4ce	nuke node so you can compile assets ... Change-Id: Ifec01be0eb6534f7d4325c2761ee5a00d76d0dcc Reviewed-on: https://gerrit.instructure.com/100510 Tested-by: Jenkins QA-Review: August Thornton <august@instructure.com> Reviewed-by: August Thornton <august@instructure.com> Product-Review: Nathan Mills <nathanm@instructure.com>	2017-02-06 19:53:29 +00:00