-
Notifications
You must be signed in to change notification settings - Fork 48
Issues: npm/normalize-package-data
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[FEATURE] “fixed” description is often less relevant than nothing
feature
#89
opened May 25, 2017 by
Haroenv
[BUG] Just because a package has a preinstall doesn't mean it doesn't have a gypfile
bug
#75
opened Apr 13, 2016 by
gabrielschulhof
[FEATURE] Use validate-npm-package-name to validate package names
feature
#54
opened Nov 17, 2014 by
iarna
[FEATURE] repositories will take precedence over repository
feature
#23
opened Apr 29, 2013 by
myrne
[FEATURE] some should-be-array fields are not guaranteed to be an array
feature
#21
opened Apr 29, 2013 by
myrne
[QUESTION] What should happen with empty or invalid bugs field?
question
#16
opened Apr 12, 2013 by
myrne
[QUSTION] Move value-inference functions into separate module?
question
#14
opened Apr 9, 2013 by
myrne
[QUESTION] Have a way to just check for correctness (i.e. whether there are warnings) ?
question
#12
opened Apr 8, 2013 by
myrne
[QUESTION] Does original code accept empty name and/or version string?
question
#7
opened Apr 8, 2013 by
myrne
[QUESTION] Is it correct to "throw" on invalid name and/or invalid version?
question
#6
opened Apr 8, 2013 by
myrne
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.