3 ms·
I don't understand why there is this issue. We publish our internal npm packages in the @company namespace and we own this namespace on the public npm registry.
by forty 6y ago
I don't understand why there is this issue. We publish our internal npm packages in the @company namespace and we own this namespace on the public npm registry. Problem solved, isn't it?
- andrethegiant 6y agoYes, I'm confused by this too. Scoped packages on npm solves this problem, yet it isn't mentioned in the article at all.