Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Failed to load plugin '@typescript-eslint' in v1.3.1 #107

Closed
markgoodyear opened this issue Apr 5, 2024 · 2 comments
Closed

[Bug]: Failed to load plugin '@typescript-eslint' in v1.3.1 #107

markgoodyear opened this issue Apr 5, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@markgoodyear
Copy link
Member

What happened?

Upgrading build tools from 1.3.0 to 1.3.1 gives the error Unexpected token '||=' (see full log output).

Looking at the ESLint config between 1.3.0 and 1.3.1, it happens when adding plugin:@typescript-eslint/recommended to the extends property, which previously would have been missing as it was defined on the nested (incorrect) version:

module.exports = {
  globals: {
    __DEV__: true,
    __PROD__: true,
    __TEST__: true,
    wp: true,
  },
  env: {
    browser: true,
    es2021: true,
    node: true,
  },
  extends: ['airbnb', 'prettier', 'plugin:@typescript-eslint/recommended'], // <— HERE
  parser: '@babel/eslint-parser',
  parserOptions: {
    requireConfigFile: false,
    babelOptions: {
      ...babelConfig,
    },
  // ...
}

Updating on the https://github.com/bigbite/block-tabbed-content repo.

Potentially related to what @g-elwell found in #106 (comment).

Which environments are you experiencing the issue on?

CLI (macOS, Windows, etc)

Relevant log output

ERROR in [eslint] Failed to load plugin '@typescript-eslint' declared in 'BaseConfig': Unexpected token '||='
Referenced from: BaseConfig
@markgoodyear markgoodyear added the bug Something isn't working label Apr 5, 2024
@markgoodyear
Copy link
Member Author

markgoodyear commented Apr 5, 2024

Just to follow up this is project is currently running Node 14, which could be a part of the issue.

@markgoodyear
Copy link
Member Author

Confirmation of Node 14 being the issue. Closing. Hopefully helps anyone hitting this issue in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants