question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

lint broken after upgrade to eslint-config-airbnb@11.1.0

See original GitHub issue

Error

$ npm run lint
Referenced from: /path/to/project/node_modules/eslint-config-airbnb-base/index.js
Referenced from: airbnb
Referenced from: /path/to/project/.eslintrc.yml
        Configuration for rule "max-len" is invalid:
        Value "data["2"].ignoreStrings" has additional properties.
        Value "data["2"].ignoreTemplateLiterals" has additional properties.

Package versions

$ npm ls | grep eslint  
├─┬ babel-eslint@6.1.2
├─┬ UNMET PEER DEPENDENCY eslint@3.4.0
├─┬ eslint-config-airbnb@11.1.0 invalid
│ ├── UNMET PEER DEPENDENCY eslint@^3.5.0
│ └── eslint-config-airbnb-base@7.1.0
├── eslint-plugin-flowtype@2.16.0
├─┬ eslint-plugin-import@1.14.0
│ ├─┬ eslint-import-resolver-node@0.2.3
├─┬ eslint-plugin-jsx-a11y@2.2.1
├── eslint-plugin-react@6.2.0

.eslintrc

extends: airbnb

parser: babel-eslint

parserOptions:
  ecmaFeatures:
  jsx: true

plugins:
  - react
  - jsx-a11y
  - import
  - flowtype

rules:
  # Enable
  #  flowtype/define-flow-type: 1
  #  flowtype/use-flow-type: 1

  # Disable
  react/jsx-filename-extension: 0  # unsupported by react-native
  react/require-extension: 0  # deprecated. use eslint-plugin-import instead

My .eslintrc file doesn’t reference max-len, but the error is triggered. It looks like a bug in eslint-config-airbnb-base/index.js. Same issue occurs for 11.0.0 and 11.1.0

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:5

github_iconTop GitHub Comments

2reactions
AdrienLemairecommented, Sep 12, 2016

Thanks for the quick reply @ljharb . You’re right, I forgot to upgrade eslint to 3.5.0. Upgrading it fixed the error 😃

0reactions
ljharbcommented, Sep 12, 2016

@Tom910 i’m not sure what you mean. if you mean that the 7.1 release creates new errors, that’s how semver tends to work with eslint and eslint plugins/configs. If you were following the guide in the first place, the arrow-parens rule would have found no problems - if it’s giving you errors now, it’s just catching your bugs.

If you want fixed versions, use shrinkwrap in your top-level app.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Eslint-config-airbnb-typescript - npm.io
A common fix is to create a tsconfig.eslint.json file, which extends your tsconfig.json file and includes all files you are linting. { " ......
Read more >
How to install eslint-config-airbnb properly ? `UNMET PEER ...
I use nvm to install node 7.5.0 , and installed eslint globally. when I try to install eslint-config-airbnb globally. It said UNMET PEER...
Read more >
eslint/eslint - Gitter
Failed to load config "@ljharb" to extend from. from a node_module's eslint config file when I run my app with eslint-loader (that ...
Read more >
eslint-config-airbnb - npm
Airbnb's ESLint config, following our styleguide. Latest version: 19.0.4, last published: a year ago. Start using eslint-config-airbnb in ...
Read more >
Setup ESLint for React with Prettier, pre-commit and VSCode
pretty-quick will check for any unformatted files and format them using Prettier. npm i -D husky lint-staged pretty-quick. After installing ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found