4 ms·
Even better, packages should be namespaced to the parties maintaining them
by subway 10y ago
Even better, packages should be namespaced to the parties maintaining them
- tlrobinson 10y agoThat's just shuffling the problem around, people will squat on user accounts.
- rwallace 10y agoEmpirically, it doesn't just shuffle the problem around, it dramatically reduces it. On Google Code, every time you tried to create a project, the name would always be taken. On Github, every time you try to create a project, you can go ahead and use the name, and I haven't heard of anyone having trouble finding something acceptable to use for their account name.
- chrisfosterelli 10y agoThis has been supported for a long while now but it never really caught on much. It's still an option if your favourite name is taken, though.
- minitech 10y agoIs this the @a/b namespacing that requires paying monthly for names (that are longer)? That’s not going to fly for most people.
- deleted 10y ago[deleted]
- chrisfosterelli 10y agoScoped packages are free: https://docs.npmjs.com/getting-started/scoped-packages https://docs.npmjs.com/getting-started/scoped-packages In regards to length, well, that's how namespacing works. Although that is likely part of what has contributed to it receiving less traction.
- minitech 10y agoOh, I thought you needed to register an organization to use scoped packages. Thanks! (And yes, I don't mind the length... unless I'm paying for it.)