Jest fails in CI with Node 6. Using Babel 7.

🐛 Bug Report

Jest or Babel-Jest doesn’t seem to work under CI environment (be it Travis or AppVeyor) when using Node 6. With Node 8 it works fine in both CIs.

I’m using Babel 7. When tested locally with the same Node 6 version it works.

To Reproduce

I can’t reproduce it locally. See link of travis build run below.

The only difference between the CI builds and my local environment is the operating system. Travis CI is using Linux (Trusty), and AppVeyor is using Windows, whereas I’m using macOS High Sierra 10.13.4.

But I’m guessing it’s not a problem with the operating system, as both work fine when using Node 8.

Relevant packages:

"@babel/cli": "7.0.0",
"@babel/core": "7.0.0",
"@babel/preset-env": "7.0.0",
"babel-core": "7.0.0-bridge.0",
"babel-jest": "23.4.2",
"babel-loader": "8.0.2",
"jest": "23.5.0",

babel.config.js (which doesn’t seem to be running when under Node 6 in the CI):

module.exports = api => {
  const env = api.env();

  let presets = [];
  let plugins = [];

  switch (env) {
    case "test": {
      presets = ["@babel/preset-env"];
      break;
    }
  }

  return {
    presets,
    plugins
  };
};

Expected behavior

The behaviour should yield the same result as the local run with the same Node and npm version, where it passes.

Link to repl or repo (highly encouraged)

See travis build at: https://github.com/scarlettgamestudio/scarlett-framework-2/runs/16865592 for a simple use case with both Node 6 and Node 8 (this one works fine). See appveyor build (using Node 6) at: https://ci.appveyor.com/project/Apidcloud/scarlett-framework-2/build/0.0.1

[milesj]

@Apidcloud Can you try 23.6? babel.config.js support was added in that version.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.