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
{{ message }}
This repository was archived by the owner on Aug 11, 2021. It is now read-only.
Currently package name verification is done by digging into the internals of normalize-package-data. Which is ugly as sin. We should probably update to use the new validate-npm-package-name module for this. Before we do that though, npm/validate-npm-package-name#1 should be addressed.
The text was updated successfully, but these errors were encountered:
Currently package name verification is done by digging into the internals of normalize-package-data. Which is ugly as sin. We should probably update to use the new validate-npm-package-name module for this. Before we do that though, npm/validate-npm-package-name#1 should be addressed.
The text was updated successfully, but these errors were encountered: