You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to provide more trust for our packages, we should start publishing them on npm using a @node or @nodejs scope. Such as: @nodejs/undici
It is a small change that can add a new level of trust to our packages.
We can continue to publish packages under their existing names too, such that nodejs/undici is cross published to undici and @nodejs/undici, but then we should add the deprecated tag to undici so we can migrate everything to scope packages.
Net new packages should only publish under @nodejs scope.
The text was updated successfully, but these errors were encountered:
In order to provide more trust for our packages, we should start publishing them on npm using a
@node
or@nodejs
scope. Such as:@nodejs/undici
It is a small change that can add a new level of trust to our packages.
We can continue to publish packages under their existing names too, such that
nodejs/undici
is cross published toundici
and@nodejs/undici
, but then we should add thedeprecated
tag toundici
so we can migrate everything to scope packages.Net new packages should only publish under
@nodejs
scope.The text was updated successfully, but these errors were encountered: