I want to create a monorpo which will never get published on npm. Still I have to find an scope/name which is not conflicting with existing, published modules or upcoming ones because in the hoisted `node_modules` folder my monorepo folder and other node modules are in that same one folder.What is the best practice here without the need to register at NPM and reserving/block a scope name in order to avoid any potential conflict?
Submitted February 05, 2019 at 07:57AM by desmap
No comments:
Post a Comment