Unknown option: base.configFile error when running tests

[davidlukerice]

Note from Maintainers

This is reportedly an issue with npm, as you will find below.

Please install Yarn as it's reportedly correctly hoisting packages, preventing this error.

If you'd like to continue using npm, run npm ls babel-core and remove offending packages that are relying on 6.x. Additionally, file a bug report with npm.

---

Is this a bug report?

Yes

Did you try recovering your dependencies?

Yes
npm --version
6.4.1

Which terms did you search for in User Guide?

jest, test, babel, Unknown option: base.configFile

Environment

Environment:
OS: macOS 10.14
Node: 8.10.0
Yarn: 1.6.0
npm: 6.4.1
Watchman: 4.9.0
Xcode: Xcode 10.0 Build version 10A255
Android Studio: Not Found

Packages: (wanted => installed)
react: ^16.4.2 => 16.5.2
react-dom: ^16.4.2 => 16.5.2
react-scripts: 2.0.3 => 2.0.3

Steps to Reproduce

1. Migrate from create-react-app v1.1.5 following the guide at https://github.com/facebook/create-react-app/releases
2. Run the dev server and verify the app works correctly (npm start)
3. Run all tests with npm test followed by a

Expected Behavior

Tests should run and complete

Actual Behavior

I get the following error on every test

Test suite failed to run

    ReferenceError: [BABEL] {redacted}/src/setupTests.js: Unknown option: base.configFile. Check out http://babeljs.io/docs/usage/options/ for more information about options.

    A common cause of this error is the presence of a configuration options object without the corresponding preset name. Example:

    Invalid:
      `{ presets: [{option: value}] }`
    Valid:
      `{ presets: [['presetName', {option: value}]] }`

    For more detailed information on preset configuration, please see https://babeljs.io/docs/en/plugins#pluginpresets-options.

      at Logger.error (node_modules/babel-core/lib/transformation/file/logger.js:41:11)
      at OptionManager.mergeOptions (node_modules/babel-core/lib/transformation/file/options/option-manager.js:226:20)
      at OptionManager.init (node_modules/babel-core/lib/transformation/file/options/option-manager.js:368:12)
      at File.initOptions (node_modules/babel-core/lib/transformation/file/index.js:212:65)
      at new File (node_modules/babel-core/lib/transformation/file/index.js:135:24)
      at Pipeline.transform (node_modules/babel-core/lib/transformation/pipeline.js:46:16)

my setupTests.js file contains the following

import 'react-testing-library/cleanup-after-each';
import 'jest-dom/extend-expect';

Adding them to a fresh app doesn't cause an issue.

Reproducible Demo

This is an internal project, but I'll work to see if I can narrow it down at all and reproduce in a fresh install. So far I haven't figured it out.
I'm putting this issue up in the meantime to see if anyone else runs into it while migrating to v2. It also popped up at #5103 (comment), but clearing the node modules / lock / &c didn't help, nor did upgrading to node v10.

[JustinTRoss]

I had the same issue, and I'm using the same setupTests.js file, though removing this file has no effect on the outcome.

I was able to get rid of this error by deleting package-lock and reinstalling.

[Timer]

I'm not able to repo this. Can you provide a small isolated example please?

[Timer]

Please post your package.json.

[JustinTRoss]

I do have jest-dom installed. Is there a reason why that dependency should be avoided when using CRA?

// package.json

"dependencies": {
    "@material-ui/core": "^3.1.0",
    "@material-ui/icons": "^3.0.1",
    "apollo-boost": "^0.1.16",
    "emotion": "^9.2.10",
    "graphql": "^14.0.2",
    "graphql-anywhere": "^4.1.19",
    "graphql-tag": "^2.10.0",
    "idx": "^2.4.0",
    "lodash": "^4.17.11",
    "raven-js": "^3.27.0",
    "react": "^16.5.2",
    "react-apollo": "^2.1.11",
    "react-dom": "^16.5.2",
    "react-emotion": "^9.2.10",
    "react-redux": "^5.0.7",
    "react-router": "^4.3.1",
    "react-router-dom": "^4.3.1",
    "react-scripts": "^2.0.3",
    "redux": "^4.0.0",
    "reselect": "^3.0.1"
  },
  "devDependencies": {
    "eslint-config-airbnb": "^17.1.0",
    "eslint-config-airbnb-base": "^13.1.0",
    "eslint-config-prettier": "^3.1.0",
    "eslint-plugin-flowtype": "^2.50.3",
    "eslint-plugin-import": "^2.14.0",
    "eslint-plugin-jsx-a11y": "^6.1.1",
    "eslint-plugin-prettier": "^3.0.0",
    "eslint-plugin-react": "^7.11.1",
    "faker": "^4.1.0",
    "jest": "^23.6.0",
    "jest-dom": "^2.0.0",
    "lint-staged": "^7.3.0",
    "prettier": "^1.14.3",
    "react-testing-library": "^5.1.0",
    "rosie": "^2.0.1"
  }

[jambyung]

I was also able to fix this issue by deleting package-lock.json and node_modules folder and running npm install again.

[gaearon]

Sounds like an npm issue then. Use the workaround above if you bump into this.

[davidlukerice]

I was repeatedly having this problem yesterday, even with the above workaround. I added the dependencies one by one back today and was able to add them back all in without incident, so who knows what npm was having trouble with.

[gustavobini]

I am having the same issue. Cleaning node_modules and installing again did not fix it.

"dependencies": {
    "react": "^16.4.2",
    "react-dom": "^16.4.2",
    "applicationinsights-js": "^1.0.19",
    "axios": "^0.18.0",
    "history": "^4.7.2",
    "mixpanel-browser": "^2.22.4",
    "prb-components": "^0.0.131",
    "qs": "^6.5.2",
    "react-lazyload": "^2.3.0",
    "react-loadable": "^5.5.0",
    "react-mobile-picker": "^0.1.12",
    "react-modal": "^3.4.4",
    "react-redux": "^5.0.7",
    "react-scripts": "2.0.3",
    "react-scroll": "^1.7.9",
    "redux": "^4.0.0",
    "redux-thunk": "^2.3.0",
    "string-to-arraybuffer": "^1.0.0",
    "styled-components": "^3.4.5",
    "styled-react-modal": "^0.2.1",
    "universal-router": "^6.0.0",
    "validator": "^10.1.0",
    "webfontloader": "^1.6.28"
  },
  "lint-staged": {
    "src/**/*.{js,jsx,json}": [
      "eslint --fix",
      "git add"
    ],
    "src/**/*.{scss,css}": [
      "stylelint --config=.stylelintrc --fix",
      "git add"
    ]
  },
  "jest": {},
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "build:development": "env-cmd .env.development npm run build",
    "build:staging": "env-cmd .env.staging npm run build",
    "build:production": "env-cmd .env.production npm run build",
    "postbuild": "node iisConfig/iisConfig.js",
    "test": "react-scripts test",
    "eject": "react-scripts eject",
    "precommit": "lint-staged && jest",
    "eslint-all": "./node_modules/.bin/eslint --fix --ext=js --ext=jsx ./src/",
    "serve": "./node_modules/.bin/serve -s --ssl ./build"
  },
  "devDependencies": {
    "classnames": "^2.2.5",
    "cross-env": "^5.2.0",
    "env-cmd": "^8.0.2",
    "enzyme": "^3.4.4",
    "enzyme-adapter-react-16": "^1.2.0",
    "eslint-config-airbnb": "^17.1.0",
    "eslint-config-prettier": "^3.0.1",
    "eslint-plugin-prettier": "^2.6.2",
    "husky": "^0.14.3",
    "lint-staged": "^7.0.4",
    "npm-run-all": "^4.1.2",
    "prettier": "^1.11.1",
    "prop-types": "^15.6.1",
    "serve": "^6.5.8",
    "stylelint": "^9.2.0",
    "stylelint-config-standard": "^18.2.0"
  }

[jambyung]

@gustavobini what about deleting both package-lock and node_modules and installing again?

[gustavobini]

@gustavobini what about deleting both package-lock and node_modules and installing again?

Sorry, I meant to say I did both those things.