Skip to content
This repository was archived by the owner on Aug 11, 2021. It is now read-only.

Maybe update to use validate-npm-package-name #83

Open
iarna opened this issue Nov 17, 2014 · 0 comments
Open

Maybe update to use validate-npm-package-name #83

iarna opened this issue Nov 17, 2014 · 0 comments

Comments

@iarna
Copy link
Contributor

iarna commented Nov 17, 2014

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant