Environment file is not loading accurately in CircleCI about ember-cli

[NullVoxPopuli]

What's your environment.js look like, as well as which environment variables are set?

[JackHowa]

hmm it's possible that they are running in two different js environments -- config/environment.js in node, the helper function, browser. But I would still expect the config environment to be built by node?

---

Thanks for the quick response.

config/environment.js looks like essentially:

'use strict';

module.exports = function () {
  let ENV = {
    APP: {
      IS_TEST_ENV: false
    }
  };

  if (process.env.TEST_FLAG) {
    ENV.APP.IS_TEST_ENV = true;
  }

  console.log('output env', ENV.APP);

  //   output env {
  //   IS_TEST_ENV: true,
  // }

  return ENV;
};

Then, when imported into a test helper that runs prior to each qunit test the incoming value is different when logged:

import ENV from 'company/config/environment';

export default function (hooks) {
  hooks.beforeEach(function () {
    console.log(JSON.stringify(ENV.APP), 'env app');
    // {"type":"log","text":"{\"IS_TEST_ENV\":false, }}

    if (ENV.APP.IS_TEST_ENV) {
      // never gets to this
      console.log('DO SOMETHING HERE');
    }
  });
}

I've also tried directly setting the process.env directly on the initial object. I've tried using strings to set values as well. I've also tried setting the value on part of the object that's not within the app key. This works as expected locally but not within circle ci.

Note I can't use the environment incoming value because test, production, and development are already in use and mixed with other variables

[JackHowa]

Problem was a ember buld step that seemed to be the source of truth for the ember test's environment.

[NullVoxPopuli]

for testing the test environment, you'd probably want import { isTesting, macroCondition } from @embroider/macros`

if (macroCondition(isTesting()) {

}

this way, when isTesting() is false, you don't ship test code to production 🎉