admin
admin copied to clipboard
nodejs
Update npm account to "Node.js" rather than "Node.js Foundation"
It seems our npm account is called "Node.js Foundation". It'd be preferable if we renamed this to "Node.js" since there is no such thing as the "Node.js Foundation" :)
https://www.npmjs.com/~nodejs-foundation
@bnb can you confirm that it is an option in npm to change the name of an existing account and that it will have no unwanted side effects ?
I assume all links to that URL will be broken and user-scoped modules will break (change to the new name) but outside of that I'm not sure. I've never seen anyone ever complain about it so I can only assume it's mostly ok :)
I think people almost never change it either tho, so I'm not sure an absence of noise is itself a signal.
Changing your github username breaks the world, so i wouldn't be surprised if changing this one caused problems too. It might be simpler to make a new npm account (or better, org) with the proper name, and then migrate to that.
FWIW spoke a bit with a hubber who's worked on the registry in the past and they also pointed out that the packages are immutable and would still exist, they just wouldn't get updates if new versions were published under that scope. It's conceptually similar to forking. I also don't think we have any modules under that scope so it doesn't matter.
I legitimately can't think of any problems here other than getting whoever has access to log in to the correct account. I'd also be fine with @ljharb's proposal, though it'd be a pain to go through and generate new keys everywhere.
generate new keys everywhere.
What keys?
The user account was added as a backup and is basically not used in day-to-day work.
I think creating a new account, and transitioning over makes sense. That also means that anybody can do that, along with working to get the password shared though a mechanism other than the build repo which has also been suggested.
What keys?
The user account was added as a backup and is basically not used in day-to-day work.
Ah, I assumed somewhere there was an automated account.
That also means that anybody can do that, along with working to get the password shared though a mechanism other than the build repo which has also been suggested.
Happy to help facilitate this through 1Password if that's helpful
@bnb sounds good. I think you could create a new npm account with the right name, have the credentials shared through 1password and then we can ask the teams publishing packages to add that new account as another collaborator in npm.
We should enable 2FA on that new account.
I think you could create a new npm account with the right name, have the credentials shared through 1password and then we can ask the teams publishing packages to add that new account as another collaborator in npm.
I'd be happy to do this, but not sure if that's what you were suggesting :P
We should enable 2FA on that new account.
Agree, the OTP configuration can be stored in/used from 1Password.
I'd be happy to do this, but not sure if that's what you were suggesting :P
That was what I was suggesting.