Support process.env.npm_package_version Inlining

[graphemecluster]

…because Node already supports it.

Currently it seems that there are no way to include the version field in package.json without prepending cross-env NPM_PACKAGE_VERSION=$npm_package_version to the parcel commands. That's verbose, and requires cross-env to be installed.

Of course you might say, I could just import the JSON file directly by import { version } from "../package.json". But that requires manually turning resolveJsonModule on. Moreover, this will including the whole JSON file, exposing other useless information in the bundle. I hate importing things outside src either.

Some people might want npm_package_name and npm_package_description too.

[panstav]

According to the docs, you can add this to your package.json:

"@parcel/transformer-js": {
    "inlineEnvironment": ["npm_package_version"]
}

[LeoDog896]

I do think that in the spirit of node emulation, all node_package_ variables should be inlined. (NPM Docs)

[tomchen]

According to the docs, you can add this to your package.json:

"@parcel/transformer-js": {
    "inlineEnvironment": ["npm_package_version"]
}

Not only this, but user has to use "context": "browser" in targets like I just did in the commit to peerjs that's mentioned above - default context "node" can't inline process.env.npm_package_version

But why with context "node" it doesn't inline process.env.npm_package_version? if @parcel/transformer-js.inlineEnvironment sets it explicitly, it should inline it.