4 ms·
I've been holding off on yarn since npm v5 has some big performance increases, but there's (as of npm 5.3) still an issue where npm v5 deletes all `private: tru
by nailer 9y ago
I've been holding off on yarn since npm v5 has some big performance increases, but there's (as of npm 5.3) still an issue where npm v5 deletes all `private: true` packages - we've had to revert to 4.6 - and I'm a little worried a data-loss issue isn't being treated as severe.
- allover 9y agoDeletes them in what situation? Can you provide a link?
- nailer 9y agoThere's a couple of similar deletion issues, they're all linked from https://github.com/npm/npm/issues/17929 https://github.com/npm/npm/issues/17929, the deleting private one happens in all situations, eg just an npm install, see https://github.com/npm/npm/issues/17927 https://github.com/npm/npm/issues/17927
- Zekio 9y agoThat explains why I when I use npm I have 24k files in my deleted files folder only for npm to fail.. after which I remember to use yarn
- allover 9y agoRE the 2nd issue: Are you sure you even need `private: true`? Scoped modules are private by default right? I thought `private: true` was supposed to prevent publishing to npm altogether. It's odd they haven't at least triaged the issue (but you know humans/time). That said the fact it's a niche workflow (it's unclear why the user is using --no-save) and the steps to reproduce won't be doable by the team ... probably doesn't help the issue get attention.
- nailer 9y agoThe packages aren't published on npm but deployed by other means (before npm is used to install additional public packages), hence 'private' is deliberate.
- deleted 9y ago[deleted]