-
Notifications
You must be signed in to change notification settings - Fork 89
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
feature request comment-hack at the top? #1
Comments
Hey @Rolograaf thanks for the issue! Please, feel free to make a PR against this project and I'll happily merge it 😄 |
Comments should ideally be kept with the line the precede. See this package.json with build scripts. Sorting that way may not be trivial. |
Using comment markers with the same key will break, because we use |
bit offtopic sidenote: there seems to be a pseudo-standard "_readme" key https://github.com/search?q=%22_readme%22%3A+lang%3AJSON&type=code it's used in composer.lock (PHP's equivalent of npm) and others |
First: I just stumbled on this and fully satisfies my neatly needs, thanks!
But I used a hack from:
http://stackoverflow.com/questions/14221579/how-do-i-add-comments-to-package-json-for-npm-install#14221781
to make a little comment in my package.json (some dependency does not yet work in Windows, but they are working on it)
It would be nice to see the "//": "comment" above all others when it is used?
The text was updated successfully, but these errors were encountered: