is not happening, even when it'd be more intuitive to make yourpackage.json parsing follow the standard npm parsing, so that theme developer could use the file as it is (like it's supposed to).
My bad, it's the npm package normalize-package-data that specifically does those things (that package is required and used by read-package-json, so what I said still applies!)
I think the
package.json
is being required directly, so that means stuff npm does automatically like parsing people objects like:into
is not happening, even when it'd be more intuitive to make your
package.json
parsing follow the standard npm parsing, so that theme developer could use the file as it is (like it's supposed to).