feature request comment-hack at the top?

[Rolograaf]

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?

[keithamus]

Hey @Rolograaf thanks for the issue! Please, feel free to make a PR against this project and I'll happily merge it 😄

[dandv]

Comments should ideally be kept with the line the precede. See this package.json with build scripts.

Sorting that way may not be trivial.

[keithamus]

Using comment markers with the same key will break, because we use JSON.stringify which removes duplicate key names, you'd have to rework the hack to append a unique string to each comment marker, e.g. //build, //test. If you did that then we could definitely sort so that they landed on top of their respective functions.

[jcbhmr]

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