Repository navigation
CLI tools behind a Nodejs namespace #1178
Description
Not sure if this is the right place for this issue, so I am happy to move it. I opened it here because it affects multiple tools in the Node.js org.
Since the installation instructions on the Node.js tooling (ie. https://github.com/nodejs/node-core-utils, https://github.com/nodejs/changelog-maker, etc) recommend a global install, should these be put under a Node.js scope on the npm registry such as @nodejs/<packagename>?
It establishes a level of trust in the published packages ("I know this came from the Node org"), and it will hopefully help contributors avoid accidental installations of similarly named packages.
Activity
ljharb commentedon Feb 25, 2022
Perhaps they should also recommend using npx instead, since global installs are widely discouraged in the community.
danielleadams commentedon Feb 25, 2022
@ljharb yeah, we should probably do both
mmarchini commentedon Feb 26, 2022
I like the idea of using namespace but would rather not use
@nodejs, as that might encourage project specific tools to be used externally, which is not recommended. Something like@nodejs-devmaybe?mhdawson commentedon Feb 28, 2022
Or maybe even something more specific like @nodejs-dev-internal ?
mcollina commentedon Mar 2, 2022
I'm ok to use an org/scope but not
@nodejs. I'm ok with@nodejs-devbut I think@nodejs-coreis more explicit in intent.targos commentedon Mar 2, 2022
I like
@nodejs-coreor@node-core.node-core-utilscould be renamed to@node-core/utilsmcollina commentedon Mar 2, 2022
@node-core/utilshas a nice sound.MylesBorins commentedon Mar 2, 2022
+1 for @node-core
it looks like the scope is currently being squatted but if someone opens a ticket with npm support (shouldn't be me) I can look into getting us access
mhdawson commentedon Apr 5, 2023
@MylesBorins created this ticket - https://support.github.com/ticket/personal/0/2095597
danielleadams commentedon Apr 7, 2023
I think that was me that squatted on it shortly after we discussed initially. Never got around to moving this forward, but I can unsquat so we can use it.
Ethan-Arrowood commentedon May 9, 2023
Relative to the thread I just opened on admin (nodejs/admin#794) I like the idea of dev-related stuff being published under a different scope than public stuff.
Ethan-Arrowood commentedon May 10, 2023
Making a plan to solve this with @danielleadams .
mhdawson commentedon May 16, 2023
I just received notification that node-core was transferred to the nodejs-foundation account. We can now start publishing packages in that namespace.
Ethan-Arrowood commentedon May 16, 2023
Do we have
@nodejstoo? I don't think its been decided yet what the external scope will be, but i think that one was shared during collab summitmhdawson commentedon May 16, 2023
Right now we have node, node-core and pkgjs
mhdawson commentedon May 31, 2023
@danielleadams now that we have node-core what are the next steps and does this still need to be on the TSC agenda.
Ethan-Arrowood commentedon Jun 1, 2023
@mhdawson I think we need to merge nodejs/admin#795 too + make the public facing scope happen
mhdawson commentedon Jun 7, 2023
Discussed in meeting today. Those in attenance agreed should be ok to start migrating packages to the node-core namespace as we have the namespace and no objections have been raised.
Ethan-Arrowood commentedon Sep 13, 2023
I'm glad to see
@node-corewas approved. Can y'all discuss another scope for public facing modules next? Thank you! RE: nodejs/admin#794jasnell commentedon Jul 18, 2025
There's been no activity here since Sep 2023. Are there concrete actions remaining? Does this need to remain open?
Ethan-Arrowood commentedon Jul 22, 2025
I think this is particularly focussed on private / internal scoped modules and
node-corewas selected and has been used for some time. The other referenced issue is still open though but can likely be tracked in a separate TSC issue if necessary (its currently in admin) nodejs/admin#794bjohansebas commentedon Jul 22, 2025
What about this? https://github.com/nodejs/admin/blob/main/package-namespace-migration.md
Ethan-Arrowood commentedon Jul 22, 2025
Ha I didn't even realize that got merged into
main. Seems like I can also close that admin issue now too. 🚀I don't think we are publishing using the
@nodejsscope yet though, are we?jasnell commentedon Mar 25, 2026
Any concrete updates here?
Ethan-Arrowood commentedon Mar 25, 2026
I can look into the CLI tools repo and see about modifying any publishing step to use the
@nodejs-corescope and then make any necessary docs updates to Node core (or anywhere else). I may not have appropriate permissions though and the publishing step could be better suited for a TSC member. I can also see about making modules likeundiciandamaropublish under@nodejstoo.