4 ms·
RE 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 pub
by allover 9y ago
RE 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]