can't run wing.compile to create a testing simulator and to a non testing simulator in the same process

[ainvoner]

I tried this:

in the same process of my node application, I'm trying to compile to a stateful simulator (non testing mode) and to a simulator runs in a testing mode.

const nonTestSim = await wing.compile(wingfile, {
        platform,
        testing: false,
      });
const testSim = await wing.compile(wingfile, {
        platform,
        testing: true,
      });

bring util;

if util.tryEnv("WING_IS_TEST") == "true" {
  log("Running in test mode");
} else {
  log("Not Running in test mode");
}

This happened:

both simulators run in testing mode

I expected this:

the first one to work in regular mode and the last one in testing mode.

Is there a workaround?

No response

Anything else?

wing/libs/wingcompiler/src/compile.ts

Line 158 in b5fa0cb

process.env["WING_IS_TEST"] = testing.toString();

if you run two compilers in the same process, the last one will override the process.envs with the latest values…
in the console we do exactly that:

wing/apps/wing-console/console/server/src/index.ts

Line 116 in b5fa0cb

const compiler = createCompiler({

and

wing/apps/wing-console/console/server/src/index.ts

Line 136 in b5fa0cb

const testCompiler = createCompiler({

Wing Version

No response

Node.js Version

No response

Platform(s)

No response

Community Notes

• Please vote by adding a 👍 reaction to the issue to help us prioritize.
• If you are interested to work on this issue, please leave a comment.

[MarkMcCulloh]

This is a dupe of #3678 which will be addressed in #5247

[staycoolcall911]

Thanks @MarkMcCulloh - since it's a blocker for @ainvoner, let's see if we can ship that fix earlier.