CLI tools behind a Nodejs namespace

[danielleadams]

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.

Docs: https://docs.npmjs.com/cli/v8/using-npm/scope

[ljharb]

Perhaps they should also recommend using npx instead, since global installs are widely discouraged in the community.

[danielleadams]

@ljharb yeah, we should probably do both

[mmarchini]

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-dev maybe?

[mhdawson]

Or maybe even something more specific like @nodejs-dev-internal ?

[mcollina]

I'm ok to use an org/scope but not @nodejs. I'm ok with @nodejs-dev but I think @nodejs-core is more explicit in intent.

[targos]

I like @nodejs-core or @node-core.

node-core-utils could be renamed to @node-core/utils

[mcollina]

@node-core/utils has a nice sound.

[MylesBorins]

+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]

@MylesBorins created this ticket - https://support.github.com/ticket/personal/0/2095597

[danielleadams]

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]

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]

Making a plan to solve this with @danielleadams .