51–54 of 54 posts
We're using a boilerplate project from a year ago with Yarn/React and it's still behaving the same way. Of course we have some deprecation warnings, but is it really so bad to have this "If it's not broke, don't fix it" mentality?
I love npm, but there's some bug that keeps looming. I have a git based dependency (basically a dependency that's attached to https://user:password@gitlab.com/xxxxxx#branch ) I don't know why, but any time I install something specific in this project: npm i -D @types/tacos (for example) The last line of npm says this: added 9 packages and removed 15 packages in 9.69s Those 15 removed packages? Not dependency conflict…
I worked with @iarna over at npm to get a very similar bug fixed - https://github.com/npm/npm/pull/20198 . I'm pretty sure this is just a special case of that bug - if you're not on npm 6.1.0 it might be fixed there. Otherwise I'd encourage you to comment in on that PR / the attached issue with a flow to reproduce.
(That's been bloating my Electron packages for a bit in that I haven't been able to trust prune --dev not to prune dependencies of a git package.)
Earlier 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
Earlier quoted context omitted.
NTFS may not handle a bunch of small files well, but I'm pretty sure WSL isn't a virtuialization layer.
You're right (I didn't realize this): https://docs.microsoft.com/en-us/windows/wsl/faq#why-would-i...
It closes the gap on OSX for "*nix experience on a computer that can run Photoshop and Excel"