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

🐛 Biome encountered an unexpected error #564

Closed
1 task done
atheck opened this issue Oct 20, 2023 · 3 comments
Closed
1 task done

🐛 Biome encountered an unexpected error #564

atheck opened this issue Oct 20, 2023 · 3 comments
Labels
S-Needs repro Status: needs a reproduction S-Needs response Status: await response from OP

Comments

@atheck
Copy link

atheck commented Oct 20, 2023

Environment information

CLI:
  Version:                      1.3.1
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           linux

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v18.18.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "npm/10.1.0"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    true
  VCS disabled:                 true

Workspace:
  Open Documents:               0

What happened?

Source Location: crates/biome_js_analyze/src/utils.rs:110:13
Thread Name: biome::worker_7
Message: internal error: entered unreachable code: The node can't have the same range of the operator.

Expected result

No error

Code of Conduct

  • I agree to follow Biome's Code of Conduct
@ematipico
Copy link
Member

Thank you, @atheck for the report. Are you able to narrow down the cause of this issue to a single snippet?

@ematipico ematipico added S-Needs repro Status: needs a reproduction S-Needs response Status: await response from OP labels Oct 20, 2023
@atheck
Copy link
Author

atheck commented Oct 20, 2023

I'm using extends in the biome.json with a custom set of linting rules. It works when I copy those linting rules to the biome.json itself and remove the extends.

Not working:

{
  "extends": ["./lintingRules.json"]
}

Works:

{
  "linter": {
    "enabled": true,
    "rules": {
      // same rules as in lintingRules.json
    }
  }
}

@ematipico
Copy link
Member

This should be fixed, it will be available in next release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-Needs repro Status: needs a reproduction S-Needs response Status: await response from OP
Projects
None yet
Development

No branches or pull requests

2 participants