Why not package.cson?

[danielbayley]

apm publish throws No package.json file found at … when attempting to use a package.cson instead… Just wondering if this is intentional; and if so, how come?

I found the same question here https://discuss.atom.io/t/why-isnt-package-cson-supported-actually-it-is/16849

[thedaniel]

It's not intentional in the sense of "we considered it and decided not to", it just never really came up in an issue before now.. I think that with apm being a wrapper around npm which has stated it will not support cson we will likely not be supporting package.cson files in the package publishing API either.

[danielbayley]

I get that npm refuse to support it. But as you say, with apm being a wrapper around it (and clearly most of the Atom ecosystem already accesses the CSON parser) I don't see why compiling it to package.json as an intermediate step would be so bad? More on this is popping up here https://discuss.atom.io/t/how-can-we-help-you-write-packages/4268/69