search

coala / gh-board

:octocat: Kanban for GitHub Issues
https://coala-gh-board.netlify.com/
GNU Affero General Public License v3.0
21 stars 25 forks source link

Switch from npm to yarn #141

Open li-boxuan opened 5 years ago

li-boxuan commented 5 years ago

Now we are using npm, but facing some problems:

  1. We are committing package-lock.json. If a contributor uses npm@6, there will be lots of carets before version number "^1.0.2". However, if another contributor uses npm@5, there will not be carets. See https://github.com/npm/npm/issues/20434#issuecomment-386815163.

  2. An issue regarding non-optional packages. See https://github.com/coala/gh-board/pull/87

jayvdb commented 5 years ago

My understanding is that yarn has similar, or worse, problems with optional packages.

123vivekr commented 5 years ago

Node Version Manager (NVM) can be used to load specific versions of npm. So everyone can work on the same version of node and avoid issues with dependency versions. What do you think about this?

li-boxuan commented 5 years ago

I am using nvm to switch versions. But is there a good way to force everyone to use the same version of node?

bhawesh96 commented 5 years ago

https://nitayneeman.com/posts/standardizing-node.js-version-in-an-npm-package/

This looks a simple good hack to me