Apply `-bs-g` flag via environment variable

[alex35mil]

As per Discord discussion, to avoid accidental production builds with -bs-g applied via config, apply it via environment variable instead.

[bobzhang]

Do you use debug build by default, how about generating .g.js for -bs-g?

[alex35mil]

Do you use debug build by default?

Currently, I turn it on occasionally, when I need to inspect something at runtime, so not by default.

how about generating .g.js for -bs-g

Doesn't it introduce the same issue that it's required to change sources to switch the build? (e.g. change imports in js files)

[TheSpyder]

I would like this (or something similar) as well. I'm starting a new project and hoping to enable -bs-g by default in the early stages, but eventually we'll need a production output mode and it would be a shame to need bsconfig.json adjustments to toggle it.

How about a command line argument to bsb that turns on the -bs-g compiler flag? That would also allow it to be used on demand or (in my case) added to a "dev build" command.

[alex35mil]

@TheSpyder Just fyi, flag was the first thing proposed in Discord discussion but @bobzhang preferred env var way back then.

[TheSpyder]

I can still vote for a flag as my preference 😉

An environment var would be fine, though, I'd just set it temporarily e.g. BS_DEBUG=true bsb instead of bsb -debug

[ozanmakes]

I find bs-g very useful and always have it on in my bsconfig.json. I strip it away using sed for production builds.

If this is going to be implemented, I think it would be useful to have an environment variable similar to "DUNE_PROFILE" instead of one that only turns dev mode on.

[TheSpyder]

strip it away using sed for production builds

Exactly. I don't mind how it's implemented, as long as I don't have to patch the config in a build script.

[erykpiast]

Anything would be better than sed-ing the config for production build. Who is gonna make the decision here? @bobzhang?

[TheSpyder]

I'm reaching the point where I just want a way to specify a completely different bsconfig.json for my production builds

[davesnx]

I'm happy to pick up this, do we agreed on it?

Seems like having 2 different bsconfigs it's a pretty common scenario, rather than one env variable that toggles the bs-g. But both are compatible, so, can I just try to create a draft of this?

[bobzhang]

On vacation, will have a look later

[bobzhang]

how about using bsb -dev and pickup bsconfig.dev.json, would it complicate things too much?