search

twlevelup / watch_edition_react

A smartwatch simulator, built in ReactJS
MIT License
3 stars 2 forks source link

RFC: Yarn vs NPM #3

Closed watsonarw closed 7 years ago

watsonarw commented 7 years ago

Yarn or NPM? discuss.

watsonarw commented 7 years ago

From the student perspective, I think we should have a ./go script that abstracts whichever we choose away. The student should be able to just run ./go start or ./go test and not worry about whether we're using yarn or NPM behind the scenes.

See: https://www.thoughtworks.com/insights/blog/praise-go-script-part-i

raytung commented 7 years ago

In my experience, yarn is quite a lot faster than npm. But that was before the latest npm came out so I don't know what's the actual difference now.

aaron-m-edwards commented 7 years ago

Good point about the go script. However we would still require them to install yarn globally before installing.

Just for ease of installation I would say for for npm

raytung commented 7 years ago

We run everything through Docker so we don't have to worry about nvm, yarn, or npm or whatever else 😄

aaron-m-edwards commented 7 years ago

Do we really expect the students to have/setup docker?

adamhope commented 7 years ago

I commented in another thread, Docker seemed like more hassle than it was worth last time we tried it.

I don't have a preference as I haven't tried Yarn. Whichever is least obtrusive for students and doesn't make things harder for Windows users.

watsonarw commented 7 years ago

Looks like we've decided (for now at least) that we'll go with NPM. For Docker conversation, see https://github.com/twlevelup/watch_edition_react/issues/5