Parsing error: Cannot read property 'ecmaFeatures' of undefined (null)

[camux]

What version of standard?
11.01

What operating system, Node.js, and npm version?
Ubuntu, Node v9.0.0, npm 6.1.0

What did you expect to happen?
This linter warning should not appear

What actually happened?
In Atom editor appear this message in all js files
Provider: js-standard Parsing error: Cannot read property 'ecmaFeatures' of undefined (null)

My package.json
"devDependencies": {
"babel-cli": "^6.26.0",
"babel-eslint": "^8.2.5",
"babel-jest": "20.0.3",
"babel-polyfill": "^6.26.0",
"eslint": "^5.0.1",
"eslint-plugin-react": "^7.10.0",
"jest": "20.0.4",
"react-test-renderer": "^16.3.2",
"standard": "^11.0.1"
}

This problem occurs after update several devs packages

[Autre31415]

I found a way to replicate this issue:

It is caused by having both eslint 5+ and standard as dependencies in a project. The bit that was most confusing was the fact that I've witnessed many repos which have both and still work fine, but if you nuke the node_modules and package-lock.json on that project and reinstall completely fresh you will now experience this bug.

In the case of @camux updating several dev packages (likely including eslint 5) created both conditions required to expose this issue.

• Having both eslint 5+ and standard as devDeps on the project
• Having a fresh updated package-lock.json that takes these into consideration

[camux]

thanks @Autre31415 at this moment I downgrade to eslint package to version 4.19.1 and problem was solved!

[bonesoul]

any fixes for this?

[likeshumidity]

See response by @tmilar xojs issue #336:

npm install --save-dev --save-exact eslint-plugin-node@7.0.1

this fixes for me.

NOTE: I am not running xojs, just happened upon that as a fix.

[lannonbr]

With the update of Standard v12, this bug seems to be resolved.

[Kikobeats]

For me this appeared after v12 version :(

[lannonbr]

If you have a package that installs both ESLint 4.x and 5.x, this will occur to a bug with acorn

[wmhilton]

I have this problem introduced by v12. I'm not directly depending on eslint... could it be conflicting with prettier-standard?

[lannonbr]

@wmhilton Prettier-standard has a dependency of eslint@4.x so yes

[wmhilton]

Hmm... I think I'm seeing this bug even after I've removed everything depending on eslint@4.x from my project.

[Autre31415]

Hmm... I think I'm seeing this bug even after I've removed everything depending on eslint@4.x from my project.

Double check those dev dependencies to make sure, then wipe out package-lock.json and node_modules and do a fresh npm install.

[ceefour]

I am having this issue on NodeJS 8.11.1 Win64 and my only libs are:

  "dependencies": {
    "@feathersjs/express": "^1.2.7",
    "@feathersjs/feathers": "^3.2.3"
  },
  "devDependencies": {
    "nodemon": "^1.18.4",
    "standard": "^12.0.1"
  }

Is it nodemon ?

My package-lock.json is:

    "eslint": {
      "version": "5.4.0",
      "resolved": "https://registry.npmjs.org/eslint/-/eslint-5.4.0.tgz",
      "integrity": "sha512-UIpL91XGex3qtL6qwyCQJar2j3osKxK9e3ano3OcGEIRM4oWIpCkDg9x95AXEC2wMs7PnxzOkPZ2gq+tsMS9yg==",
      "dev": true,

so it's not eslint@4 conflict then?

[ceefour]

Thanks to @favadi's #1189 (comment). Workaround works for me is:

npm i --save-dev standard@11

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.