I was reading Polymer's 3.0 Preview documentation <https://www.polymer-project.org/blog/2017-08-23-hands-on-30-preview> and see that they've announced that yarn is a dependency.
Why? instead of just using NPM 5 <https://auth0.com/blog/whats-new-in-node8-and-npm5/>, which does a lot of the same things yarn does? In the summit, they have said <https://youtu.be/JH6jEcLxJEI?t=8m20s> that they needed a package manager to: 1. Manages dependencies 2. Resolves version conflicts 3. Supports a flat dependency tree 4. Has an active community AFAIK, npm already does this in later versions. So why use yarn which is unnecessary? I get that yarn may be the hot dependency manager today but a lot of people are fine with just using npm. Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/dfbe28c5-6bc4-43fa-8ae7-35c0d150b74c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
