Expose whether the command is running in dev or prod

[adam-lynch]

There's no easy way to tell whether the command is running in dev or not.

I could assume production production unless a certain environment variable exists, but that's not a great idea. It would require devs to set an environment variable (globally or when running the CLI on any machine) and if they forget, they might run something bad on a branch and it'll interact with production servers.

This is my current workaround; environment.js:

/*
	In production, commands are each bundled into a single file;
	e.g. /build/commands/index.js.
	That's why the following will be false in production
*/
const isDev = __filename.endsWith("environment.js");

export default Object.freeze({
	isDev
});

I use this in my commands/components to check if it's dev/prod
I suggest pastel sets process.env.NODE_ENV or something like that.

[adam-lynch]

That doesn't work actually... I misunderstood. What we do now is store a file outside the build directory and check it at runtime

[vadimdemedes]

That's a good catch, will need to think how to approach this.