-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use yarn to manage dependencies #1488
Comments
In addition to the benefits I already mentioned:
Using yarn made working with local checked out dependencies so easy. |
Is this similar to Generally, I think we need more examples of how yarn could be an improvement, because it can be difficult to compare them based on opinion. Also, I just want to note that I don't have a personal preference and is fine with either, I just have more experience with npm. If more people would prefer yarn, that's fine with me. |
So far I only hear positive feedback about yarn from two yarn user so it seems very opinion to me too. Would like to hear some more cons about yarn (if any) and why some still use NPM, or has recently switched to yarn or gone back and why. Have you recently benchmarked with latest npm and or npm ci? while we are comparing npm and yarn - why don't we throw in pnpm to the mix also? that is also yet another package mananger Speaking for myself:
just some small research: My philosophy have been to stick with what i know and will last forever and don't follow in one others footstep. NPM is here to stay and will always be shipping along side with NodeJS For example: Learning CoffeeScript would have been a mistake and updating to es6/7 would be fun. The thing is, they will always be one step behind with JavaScript. Sure they may add features but when javascript changes then CoffeeScript needs to follow. I'm also just waiting until the day javascript adds type support... Making TypeScrip obsolete and unnecessary. have fun updating (I'm sticking with js). |
Why not add At this point all package managers are aware of how dependencies are handled based on Plus, After NPM 6, I don't feel much difference between npm and yarn. but when comes to comparison between two. I vote yarn. |
I have to admit that I did not use npm a lot recently, so it may be that they have catched up on things I am not yet aware of.
git clone https://github.com/Borewit/music-metadata.git
cd music-metadata
# yarn install and yarn build would be required to get it to work
# The following step only has to be done once, as long as the local path remains the same
yarn link
cd ..
# Now you can use the local dependency anywhere you like
git clone https://github.com/webtorrent/webtorrent-desktop.git
cd webtorrent-desktop
yarn link music-metadata Looking at npm link, that looks pretty similar. For some reason I was strugling with npm, and it seems work as it should with yarn.
Fair point @sibiraj-s; I updated the issue description. |
@jimmywarting because you are not planning to use it. What is your final vote Jimmy? |
can i have 2 vote? either no-lock or npm |
decided? |
I don't see a collective thumbs of for yarn, so I guess we continue with npm and the corresponding lockfile. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Background
Based on a disussion started here, I propose to continue the discussion here.
Do we want to check in a lock file?
And if we do, which one?
Do we want to:?
Votes:
Pending / not clear: @mathiasvr
The text was updated successfully, but these errors were encountered: