You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the point of the new version of Yarn is that we'd like for people to be able to pull a repo and have all dependencies, and for this to work forever in the future; should we also commit the Node.js binary?
Describe the drawbacks of your solution
Bigger Git-repo size for projects
Would have to commit binaries for different platforms (unless one could use something like cosmopolitan)
New binary files every time one needs to update Node.js
Describe alternatives you've considered
Not doing that at all. Instead using tools like nvm and volta to manage Node.js versions. That however introduces yet another tool that isn't commited to the git repo and that a developer (and a buildserver) have to install.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
If the point of the new version of Yarn is that we'd like for people to be able to pull a repo and have all dependencies, and for this to work forever in the future; should we also commit the Node.js binary?
Describe the drawbacks of your solution
Describe alternatives you've considered
Not doing that at all. Instead using tools like nvm and volta to manage Node.js versions. That however introduces yet another tool that isn't commited to the git repo and that a developer (and a buildserver) have to install.
Beta Was this translation helpful? Give feedback.
All reactions