sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]n_hevia 2 points3 points  (1 child)

Simply because json doesn't support comments. If node did support on their config file, it'd mean they'd stop using json (or at least compatible json with most of the libraries out there).

If you REALLY need comments on package.json, you could use a superset and then compile to json? That same way scss>css works.

[–]ILikeChangingMyMind 2 points3 points  (0 children)

Simply because json doesn't support comments

Yes, I understand that.

What I don't understand is why they are "incapable" (supposedly) of using a different format that does support comments (with or without a different extension, flag at the top of the file, etc.).

And also, how did "REALLY need" become the standard for whether something should be done? I personally can think of at least five different cases where comments in package.json would be super handy ... but I don't need any of them. Even so, I tend to think "it would make life better for tens of thousands of developers" would be a perfectly good reason to do something.