-
Notifications
You must be signed in to change notification settings - Fork 29
🚀 Feature: Use npm modules for validation #44
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
Comments
This would be great: the closer this package gets to the npm spec, the better! Per #78 I'm still ramping up on this project, so I don't want to take on any big changes anytime soon. Marking this one as |
This should be included in the new modular |
@all-contributors please add @jasonkarns for ideas.
|
I've put up a pull request to add @jasonkarns! 🎉 |
Adds @jasonkarns as a contributor for ideas. This was requested by JoshuaKGoldberg [in this comment](#44 (comment)) --------- Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
The
version
field probably ought to be validated using the semver module, and thelicense
field probably ought to be validated using the spdx module. Both of these are used by normalize-package-data which in turn is used by npm itself when parsing the package.json.Other parsing/validation rules (for the npm spec, at least) ought to be brought in line with the normalization rules from normalize-package-data
The text was updated successfully, but these errors were encountered: