-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package scope migration plan #795
base: main
Are you sure you want to change the base?
Conversation
|
||
Packages intended to be used directly by general developers should be published under the `@nodejs` namespace. Packages intended to be used only by Node.js contributors should be published under the `@node-core` namespace. | ||
Packages intended to be used directly by general developers should be published under the `@nodejs` scope. Packages intended to be used only by Node.js contributors should be published under the `@node-core` scope. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not a big deal, but why not nodejs-core?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See discussion here: nodejs/TSC#1178
Adding this to PR description
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gotcha. I don’t see any reasons there to avoid the consistency, but it’s not a big deal either way.
Ticket - https://support.github.com/ticket/personal/0/2186574 to request the nodejs org for the nodejs-foundation user. |
Any status on that ticket? We are looking to use it in undici |
This PR adds a document detailing the plan to introduce package scope for Node.js
See discussion here: nodejs/TSC#1178 for more details, and a similar post here: #794