Introducing Yarn 2! 
https://yarnpkg.com/dev-article.html …
While I'm excited by this release and love Yarn in general, I'm a little surprised Yarn is "still a thing" (and that we definitely still need it). Is there a story behind why Yarn is it's own project and not just improvements to npm?
-
-
It's a funny question I never know how to answer - would you suggest Rollup and Webpack to merge? Yarn and npm have fundamental differences in term of implementation, tradeoffs, goals, roadmaps, core communities.
-
In a sense, they are two very separate projects that just happen to use part of the same package.json format - similar to how Rollup and Webpack both work with JS files and import statements, but that's pretty much where the similarities stop.
Kraj razgovora
Novi razgovor -
-
-
npm lost me when I discovered npm install didn't respect package-lock.json, and that the "fix" was to introduce a new command, npm ci…makes no sense to me.
-
yarn is no better in that regard. `yarn install --frozen-lockfile` is basically the equivalent to `npm ci`. See:https://github.com/yarnpkg/yarn/issues/4147 …
- Još 1 odgovor
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.