Packages for `doc-kit`

[avivkeller]

@nodejs/TSC this item has a deadline of August 12th due to RenderATL

@nodejs/web would like the following npm packages set up with identical OIDC to @node-core/doc-kit:

• @nodejs/doc-kit
• @nodejs/doc-kit-generator-react
• @nodejs/doc-kit-generator-legacy

[mcollina]

Why @nodejs and not @node-core? We have zero packages at @nodejs holding it for some reasons (possibly publishing official modules etc). It requires a longer discussion (unfrotunately), so I don't think we can meet your deadline.

@node-core would do?

[legendecas]

https://www.npmjs.com/package/@node-core/doc-kit was published under @node-core

[mcollina]

No problem for publishing them in @node-core.

[avivkeller]

@mcollina Following the https://github.com/nodejs/admin/blob/main/package-namespace-migration.md, the web team voted that it would be best to publish doc-kit under @nodejs, since it's a general tool rather than a Node.js-core-only utility.

@node-core/doc-kit would remain the doc-kit + Node.js Core utilities needed for building Node.js docs

[legendecas]

FWIW, https://www.npmjs.com/org/nodejs does not show who has access to this scope, but we do not have access to it on the account https://www.npmjs.com/~nodejs-foundation.

I traced to #795 (comment) but I don't have access to the github ticket.

[Ethan-Arrowood]

I don't know what longer discussion is necessary. We seemingly agreed to the @nodejs scope plan years ago but then never actually acted on it. I don't have access to the scope on npm, but I'd love to see us publish undici and amaro on it. ++ for doc-kit packages too!

[ovflowd]

Aaand, we can ask the npm team to give it ownership to us as it is our trademark in case we all lost access to it.

[legendecas]

Can someone clarify what the difference of the proposed @nodejs/doc-kit and the existing @node-core/doc-kit?

[avivkeller]

Can someone clarify what the difference of the proposed @nodejs/doc-kit and the existing @node-core/doc-kit?

The plan was:

• Everything currently in @node-core/doc-kit will be moved to @nodejs/doc-kit prior to RenderATL so it's clear this is a general package, not a node-core-only dependency
• @node-core/doc-kit would publish a major, changing it to only contain the Node.js specific branding (e.g. Logos, green, etc) needed to generate the Node.js documentation from the general @nodejs/doc-kit-generated output

[ovflowd]

@legendecas in this repository there is a document describing what packages should be under what scope, unsure if you are familiar with it.

brian, moderator edit: linked to the document

[legendecas]

I am aware of it and as mentioned in #1082 (comment), we don't have access to @nodejs right now. As traced to #795 (comment), I don't have visibility into the github ticket.

Regardless of @nodejs access, a consensus is still needed to publish new packages to @nodejs. So I believe my ask of clarification is a fair ask, given the established @node-core/doc-kit precedence.

[ovflowd]

I am aware of it and as mentioned in #1082 (comment), we don't have access to @nodejs right now. As traced to #795 (comment), I don't have visibility into the github ticket.

Regardless of @nodejs access, a consensus is still needed to publish new packages to @nodejs. So I believe my ask of clarification is a fair ask, given the established @node-core/doc-kit precedence.

To clarify, not questioning your ask. Just wanted to triple-check you knew that document, because I also only discovered that recently.

[legendecas]

I took a look into the process of npm name dispute, tracking it separately in #1083.

Given the deadline August 12th mentioned on this issue, I would not rely on the fact that we could publish to @nodejs namespace before then.

[avivkeller]

Given the deadline August 12th mentioned on this issue, I would not rely on the fact that we could publish to @nodejs namespace before then.

That's unfortunate. Let's give ourselves the benefit of the doubt, but if we can't get the namespace by Friday, let's publish to @node-core, with those names being:

• @node-core/doc-kit-generator-react
• @node-core/doc-kit-generator-legacy
• @node-core/doc-kit-node-internals

Hopefully we get this before then