Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Why not use a scoped package for nps? #254
I'm second guessing my decision to scope my npm packages… pretty much all packages I use are not scoped. Brought this up here too: http://stackoverflow.com/questions/42377534/is-the-lack-of-scoped-npm-packages-due-to-recency-of-this-feature
What's your stand on npm scoped packages? When publishing your modules, do you intentionally avoid scoping them?
Personally, I think this is the best reason against scoped pkgs (in certain cases): "They can make it difficult/awkward to transfer ownership of the project"
Re difficult to remember:
Re the transfer of ownership of the project. Ye, I'll have to admit that bugs me too. My current mindset is that if it's a "micro" package, something that does only one thing (and that one thing is pretty small) - then I'm quite comfortable scoping it. It's unlikely to need too much maintaining after writing. Also, anyone can easily fork the project and publish under their username. The point of the pkg is to not have to repeat code if it's already written.
If the pkg isn't just a function or two, I think I'll stick with unscoped