> We've published an open-source module called deyarn to help you convert your projects from Yarn to npm! Would have been cool to call it "untie" or "untangle"
I've used synp. It works both ways
To Yarn and Back to Npm Again
41–50 of 54 posts
Re: To Yarn and Back to Npm Again
#42Just the way npm handled my bug reports made me decide never use npm cli again. The registry is something everyone has to use because npm has a monopoly. It's not open source and is making money for a for profit company. I'm very disappointed to see Node.js is still shipping this anti-foss OSS with its executables :(
Try running a repo for free : ) As you might infer from my comments I'm not the biggest fanboy but criticising them over running a freely available repo that the community has used for years feels a little bit wrong
npm CLI is run by Npm Inc. Npm makes money by maintaining the CLI as their primary selling point. for profit. Yarn is also have many paid engineers from Facebook and Google contributing to it as their day job.
These things are not real free open source software by any means
Re: To Yarn and Back to Npm Again
#43The reason I can't stand npm is that a lot of their employees are extremely vocal massive cunts.
Re: To Yarn and Back to Npm Again
#44In any other tech company, the employee would get booted asap for sharing toxic, hateful stuff.
Re: To Yarn and Back to Npm Again
#45Earlier quoted context omitted.
Try running a repo for free : ) As you might infer from my comments I'm not the biggest fanboy but criticising them over running a freely available repo that the community has used for years feels a little bit wrong
npm CLI is run by Npm Inc. Npm makes money by maintaining the CLI as their primary selling point. for profit. Yarn is also have many paid engineers from Facebook and Google contributing to it as their day job. These things are not real free open source software by any means
Free open source does not mean "not for profit".
This is actually an important thing.
Huge parts of the largest open source projects comes from "paid engineers from Facebook and Google contributing to it as their day job" or even from IBM, Microsoft or Oracle employees.
What matters is that it is released as open source so we can maintain it or pay someone else to do it.
The special thing about npm is they also run the package repo but even there I'd say they played nicely by allowing free use and not discouraging alternative clients.
Re: To Yarn and Back to Npm Again
#46Still getting data loss with npm 5 and 6: https://github.com/npm/npm/issues/17927#issuecomment-3930336...
Re: To Yarn and Back to Npm Again
#47Re: To Yarn and Back to Npm Again
#48can somebody tell me why the thumbnail of this page shows report data with probably private email data? (see og:image meta tag on that page)
Re: To Yarn and Back to Npm Again
#49can somebody tell me why the thumbnail of this page shows report data with probably private email data? (see og:image meta tag on that page)
This sounded interesting, but turns out it's just the screenshot from their homepage [0]
Re: To Yarn and Back to Npm Again
#50yarn is still better than npm. You are making a grave mistake.