Documentation URL

https://biomejs.dev/guides/how-biome-works/#glob-syntax-explained

Description

Looks like the layout is somehow messed up and IIRC we don't use globset in our codebase, so refering to globset is probably wrong.

Expectations

The content should be correct and organized properly.

Code of Conduct

• I agree to follow Biome's Code of Conduct

Documentation URL

https://biomejs.dev/linter/rules/use-import-restrictions/

Description

Using typescript code actions Add missing imports results in code that is reported by biome. I am using the default typescript language server settings.

// biome reports `noUndeclaredDependencies`
import MyModule from "src/main"; // <- this line is auto-generated by "add missing imports"

// biome does not report`noUndeclaredDependencies` when changed to this:
import MyModule from "../main";

// biome reports `useImportType`
import MyModule from "module"; // <- this line is auto-generated by "add missing imports"
// …
let mod: MyModule;

While I think the first can be resolved by changing the typescript configuration to importModuleSpecifierPreference = relative (see here), I am not aware of any typescript setting to deal with the latter. (preferTypeOnlyAutoImports does that, see comment below)

Expectations

That a recommended rule (useImportType) reports output of typescript as an issue is quite irritating, and probably very confusing for less experienced users.

You could argue that this is somewhat a bug of those rules, but technically, the rules work as expected. Possible solutions to this:

A) Change the documentation

1. Mention that these rules oppose the output of typescript code actions with default settings.
2. Explain which typescript settings need to be changed to make the output of the code actions comply with biome's rules.

However, 2. is complicated by the fact that there is (to my knowledge) no typescript setting to make typescript add type imports instead of imports. (preferTypeOnlyAutoImports does that, as commented below)

Also, changing typescript configs is not always straightforward. Since tsserver is not "fully" open, users with an editor other than VSCode need to install special language server replacements to be able to configure the typescript.preferences, e.g. typescript tools.

That means: Quite a lot of effort to be able to comply with biome for new users.

B) Change rule behavior

Alternatively, the rule's behavior should be modified to be less strict. noUndeclaredDependencies could be modified to check if an import is simply project-relative, before reporting a violation.

Not sure how to deal with useImportType though. I'd consider demoting it from a recommended to a purely opt-in rule.

Code of Conduct

• I agree to follow Biome's Code of Conduct

See https://github.com/biomejs/biome/blob/60e67bf3421362094a2edc75052bdfcffd6e2eb7/.github/workflows/label-issue.yaml#L12-L23

Documentation URL

https://biomejs.dev/

Description

Not able to access the site/documentation. This happened earlier also, but got resolved. Now it has been down for quite some time and we are not able to access any documentation.

Expectations

We should be able to access the website securely.

Code of Conduct

• I agree to follow Biome's Code of Conduct

Environment information

CLI:
  Version:                      1.8.0
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v21.7.1"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "npm/10.7.0"

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

Workspace:
  Open Documents:               0

What happened?

1. npx @biomejs/biome init generates this biome.json:

   {
       "$schema": "https://biomejs.dev/schemas/1.8.0/schema.json",
       "organizeImports": {
    	   "enabled": true
       },
       "linter": {
    	   "enabled": true,
    	   "rules": {
    		   "recommended": true
    	   }
       }
   }
   

2. The advertised schema links to a 404 page.

Expected result

The schema should be available at the URL generated by npx @biomejs/biome init

Code of Conduct

• I agree to follow Biome's Code of Conduct

Documentation URL

https://biomejs.dev/

Description

The above link (https://discord.com/invite/BypW39g6Yc) opens in Discord, saying it's an invalid link

Expectations

I expected to open Discord into the Biome server

Code of Conduct

• I agree to follow Biome's Code of Conduct

Documentation URL

https://biomejs.dev/ja/recipes/git-hooks/

Description

The git error log output by Lefthook outputs ANSI escape code as is, so we need to add an option to display plain text.

> git -c user.useConfigOnly=true commit --quiet --allow-empty-message --file -
╭───────────────────────────────────────╮
│ 🥊 lefthook v1.7.11  hook: pre-commit │
╰───────────────────────────────────────╯
sync hooks: ✔️ (pre-commit)
┃  check ❯ 

�[0m.//src/lib/Foo/Foo.tsx�[0m�[0m:�[0m�[0m4�[0m�[0m:�[0m�[0m34�[0m�[0m �[0m�[0mparse�[0m�[0m �[0m�[0m━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━�[0m�[0m
...

Expectations

It took me a little while to get to this information, but wouldn't it be more helpful to include it by default in the Lefthook Example in the Git Hook section?

```yaml title="lefthook.yml"
pre-commit:
  commands:
    check:
      glob: "*.{js,ts,cjs,mjs,d.cts,d.mts,jsx,tsx,json,jsonc}"
      run: npx @biomejs/biome check --no-errors-on-unmatched --files-ignore-unknown=true --colors=off {staged_files}

P.S
I was going to make a PR but I didn't have the authority to do so 😿.

Code of Conduct

• I agree to follow Biome's Code of Conduct

The current cache settings of the action setup-rust are not working well. We've reached the limit and the caches are not being restored or saved properly. This also slows down the codegen job.

I'll look into it.

Environment information

e.g.

switch (getStringProperty(error, 'code')) {
  case 'EACCES':
    console.error(`${bind} requires elevated privileges`);
    process.exit(EXIT_ERROR);
  case 'EADDRINUSE':
    console.error(`${bind} is already in use`);
    process.exit(EXIT_ERROR);
  default:
    throw error;
}

Gives error

error.ts:86:7 lint/suspicious/noFallthroughSwitchClause ━━━━━━━━━━

  ✖ This case is falling through to the next case.
  
    84 │     // handle specific listen errors with friendly messages
    85 │     switch (getStringProperty(error, 'code')) {
  > 86 │       case 'EACCES':
       │       ^^^^^^^^^^^^^^
  > 87 │         console.error(`${bind} requires elevated privileges`);
  > 88 │         process.exit(EXIT_ERROR);
       │         ^^^^^^^^^^^^^^^^^^^^^^^^^
    89 │       case 'EADDRINUSE':
    90 │         console.error(`${bind} is already in use`);
  
  ℹ Add a `break` or `return` statement to the end of this case to prevent fallthrough.

However, adding a return or break gives a typescript error saying unreachable code detected.

Rule name

lint/suspicious/noFallthroughSwitchClause

Playground link

https://biomejs.dev/playground/?indentStyle=space&quoteStyle=single&importSortingEnabled=false&code=cwB3AGkAdABjAGgAIAAoAGcAZQB0AFMAdAByAGkAbgBnAFAAcgBvAHAAZQByAHQAeQAoAGUAcgByAG8AcgAsACAAJwBjAG8AZABlACcAKQApACAAewAKACAAIABjAGEAcwBlACAAJwBFAEEAQwBDAEUAUwAnADoACgAgACAAIAAgAGMAbwBuAHMAbwBsAGUALgBlAHIAcgBvAHIAKABgACQAewBiAGkAbgBkAH0AIAByAGUAcQB1AGkAcgBlAHMAIABlAGwAZQB2AGEAdABlAGQAIABwAHIAaQB2AGkAbABlAGcAZQBzAGAAKQA7AAoAIAAgACAAIABwAHIAbwBjAGUAcwBzAC4AZQB4AGkAdAAoAEUAWABJAFQAXwBFAFIAUgBPAFIAKQA7AAoAIAAgAGMAYQBzAGUAIAAnAEUAQQBEAEQAUgBJAE4AVQBTAEUAJwA6AAoAIAAgACAAIABjAG8AbgBzAG8AbABlAC4AZQByAHIAbwByACgAYAAkAHsAYgBpAG4AZAB9ACAAaQBzACAAYQBsAHIAZQBhAGQAeQAgAGkAbgAgAHUAcwBlAGAAKQA7AAoAIAAgACAAIABwAHIAbwBjAGUAcwBzAC4AZQB4AGkAdAAoAEUAWABJAFQAXwBFAFIAUgBPAFIAKQA7AAoAIAAgAGQAZQBmAGEAdQBsAHQAOgAKACAAIAAgACAAdABoAHIAbwB3ACAAZQByAHIAbwByADsACgB9AA%3D%3D

Expected result

It should not display an error

Code of Conduct

• I agree to follow Biome's Code of Conduct

We don't need SASS now that the majority of the browsers support CSS nesting.

Edit: Referencing this issue for visibility in biomejs/biome#2228 in order to help track down any related issues should this be resolved/supported.

Environment information

CLI:
  Version:                      1.6.3
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           windows

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

Biome Configuration:
  Status:                       unset

Workspace:
  Open Documents:               0

What happened?

It's a little bit hard to replicate my setup with the playground links due to the shared config package and ci nature.

Example run in ci: https://github.com/exile-watch/nucleus/actions/runs/8441346324/job/23120305017#step:2:252

Here is the shared config: https://github.com/exile-watch/splinters/blob/main/packages/biome-config/biome.json#L30-L34

Here is how it's utilized: https://github.com/exile-watch/nucleus/blob/main/packages/encounter-data/biome.json

And here is a package json that has tabs instead of spaces: https://github.com/exile-watch/nucleus/blob/main/packages/encounter-data/package.json

Locally everything is passing when i go with npm run format or npm run lint but for some reason the ci command fails

Another potential issue I've noticed, though this one is with pre-commit git hooks, is that the recipe command in biomejs.dev site is resetting any format/lint --apply changes (which also gives an indication of somewhat ignoring some rules from shared config)

pre-commit:
  commands:
    check:
      glob: "*.{js,ts,cjs,mjs,d.cts,d.mts,jsx,tsx,json,jsonc}"
      run: npx biome check --no-errors-on-unmatched --files-ignore-unknown=true {staged_files}

this one in particular, but I can "easily" bypass that by changing the run script to npm run lint so it can respect my shared config

Expected result

I wouldn't expect indent errors to appear in ci.

Code of Conduct

• I agree to follow Biome's Code of Conduct

We recently fixed an issue where the important sorting doesn't move side effect modules anymore, however this isn't documented.

Description

For example, https://biomejs.dev/linter/rules-sources/ does not include Stylelint as a source, and does not contain https://biomejs.dev/linter/rules/no-unknown-function.

I cannot access https://biomejs.dev/ from my Macbook. I can from my iPhone and my Windows PC. I'm on my personal network and I don't see any issue with any other sites.

I'm using Arc browser on my Macbook and Windows, Safari on my iPhone. I'm on the same Wifi network for all of them, so I have a feeling its something related. On another Macbook, I wasn't able to access this site either. I'm not using an ad block. My firewall is not active. I'm a bit at a loss!

Please let me know if you need anymore information!

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): update dependency @types/react to v18.3.4
• chore(deps): update dependency vite to v5.4.2
• chore(deps): update dependency astro to v4.14.5
• chore(deps): update dependency cm6-graphql to v0.1.0
• chore(deps): update pnpm to v9.8.0
• fix(deps): update rust crate pulldown-cmark to 0.12.0
• chore(deps): update dependency mermaid to v11

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency autoprefixer to v10.4.20
• chore(deps): update dependency postcss to v8.4.41

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Documentation URL

https://biomejs.dev/linter/rules/no-implicit-boolean/

Description

Biome lint/style/noImplicitBoolean does the opposite of the default react/jsx-boolean-value.

Current "Same as: react/jsx-boolean-value" is misleading as the default behavior of the ESLint rule is about removing the implicit values and lint/style/noImplicitBoolean has no way to achieve it.

Expectations

Do not say it is "same as".

Code of Conduct

• I agree to follow Biome's Code of Conduct

Description

Not an issue, more of a documentation feature request.

In the lint rules listing, every rule has flags about stability and if fixable or not (https://biomejs.dev/linter/rules/), example:

but the rule detail page is missing the information, example:

Expectations

We have strong control over every configuration in the project so when new Biome version is released, we go through the changelog and evaluate every new rule. Right now, we have to find every rule in the listing to see those flags. It would be great to have those icons in the rule detail page too 🙂

Code of Conduct

• I agree to follow Biome's Code of Conduct

Documentation URL

https://biomejs.dev/ja/guides/getting-started/

Description

Test

Expectations

Test

Code of Conduct

• I agree to follow Biome's Code of Conduct

Documentation URL

https://biomejs.dev/linter/rules/

Description

Most users will use recommended preset, discovering what other rules might be useful would require going to a site and manually filtering which rules are not enabled by default. Making it hard to keep up, especially after new version releases.

Expectations

Likely something similar how to typescript-eslint allows to filter rules based on categories.

Code of Conduct

• I agree to follow Biome's Code of Conduct

I create pr here:
#499

npx biome commands should be npx @biomejs/biome

Display Biome and Prettier versions in the playground so we can have a clear understanding and expection of their behaviors.

• For Biome, the version is the commit hash and a user can click it to browse that specific commit in the biomejs/biome repo.
• For Prettier, we use its release version.

Documentation URL

https://biomejs.dev/linter/rules/no-evolving-any

Description

Follow up on biomejs/biome#1883 biomejs/biome#2112

The docs currently state that evolving types may lead to variables with an any type, but lack any sort of examples which demonstrate this. It is also stated that evolving any disables many type-checking rules, also without any examples or references.

Expectations

What are the exact caveats of using evolving any? What are the examples?

From what I know, evolving any doesn't turn into any if not explicitly assigned as such. Just like it doesn't disable many type-checking rules. I might be wrong, but the docs lack any proofs or references.

Code of Conduct

• I agree to follow Biome's Code of Conduct

Documentation URL

https://biomejs.dev/linter/rules/no-redundant-use-strict/

Description

the noRedundantUseStrict shows removing redundant strict -- and the biome playground allows for both "Module" and "Script" forms -- but I can't find how to configure that from the cli and so I am always getting a diagnostic for removal of 'use strict';

Expectations

it may be nice to show how to teach biome that these are scripts and not modules -- perhaps in the noRedundantUseStrict docs as well since that's where it is relevant to me!

Code of Conduct

• I agree to follow Biome's Code of Conduct

Documentation URL

https://biomejs.dev/linter/rules/

Description

At the very top of the page, it explains what each icon means what:

Below the list of rules supported by Biome, divided by group. Here’s a legend of the emojis:

• The icon indicates that the rule is part of the recommended rules.
• The icon indicates that the rule provides a code action (fix) that is safe to apply.
• The icon indicates that the rule provides a code action (fix) that is unsafe to apply.
• The icon indicates that the rule is applied to JavaScript and super languages files.
• The icon indicates that the rule is applied to TypeScript and TSX files.
• The icon indicates that the rule is applied to JSON files.
• The icon indicates that the rule is applied to CSS files.

But this page is too long; scrolling little bit I forgot what stands for, more scrolling I forgot what stands for, and after the half of the doc only I can remember was and . There's no mouseover tooltip in icons, so I have to scroll back to the top.

Expectations

One could be a tooltip, like moving from existing aria-label to title:

<span class="inline-icon" title="The rule has a safe fix" role="img">
  <Icon name="seti:config" />
</span>

Or one could be a text label instead of icons, for clear meaning. I think it can be short enough to label as a text.

<td>
  <span class="badge">Recommended</span>
  <span class="badge">Safe fix</span>
  <span class="badge">CSS</span>
</td>

Code of Conduct

• I agree to follow Biome's Code of Conduct

Documentation URL

https://biomejs.dev/guides/getting-started/#configuration

Description

After following the documentation guide for Bun, when running bunx @biomejs/biome init, an error occurred stating error: Script not found "@biomejs/biome".

❯ bun add --dev --exact @biomejs/biome
bun add v1.1.18 (5a0b9352)

$ bun run sync
$ bunx --bun svelte-kit sync

installed @biomejs/[email protected] with binaries:
 - biome

[1243.00ms] done

❯ bunx @biomejs/biome init
error: Script not found "@biomejs/biome"

I think the correct command to use is bunx biome init.

❯ bunx biome init

Welcome to Biome! Let's get you started...

Files created 

  - biome.json
    Your project configuration. See https://biomejs.dev/reference/configuration

Next Steps 

  1. Setup an editor extension
     Get live errors as you type and format when you save.
     Learn more at https://biomejs.dev/guides/integrate-in-editor/

  2. Try a command
     biome check  checks formatting, import sorting, and lint rules.
     biome --help displays the available commands.

  3. Migrate from ESLint and Prettier
     biome migrate eslint   migrates your ESLint configuration to Biome.
     biome migrate prettier migrates your Prettier configuration to Biome.

  4. Read the documentation
     Find guides and documentation at https://biomejs.dev/guides/getting-started/

  5. Get involved with the community
     Ask questions and contribute on GitHub: https://github.com/biomejs/biome
     Seek for help on Discord: https://discord.gg/BypW39g6Yc

Expectations

Should not output error.

Code of Conduct

• I agree to follow Biome's Code of Conduct

Documentation URL

https://biomejs.dev/ja/reference/configuration/

Description

miss typo VSCクライアント

path: src/content/docs/ja/reference/configuration.mdx Line 128

Expectations

Correct typo VCSクライアント

path: src/content/docs/ja/reference/configuration.mdx Line 128

Code of Conduct

• I agree to follow Biome's Code of Conduct

Description

In the Playground we can add a JSON file. Biome correctly recognized it as JSON and format this as a JSON file. Prettier seems to recognize the file as JavaScript, because it removes the quotes around the property.

See this Playground example.

The Playground should correctly inform Prettier than the file is a JSON file.

Documentation URL

https://biomejs.dev/guides/getting-started/

Description

I recently contributed a new regex preset to Renovate to assist with automating the $schema version inline with the biomejs npm releases.

renovatebot/renovate#28537

Expectations

Consider documenting how mutual users of biome and renovate can use this preset

Preset documentation: https://docs.renovatebot.com/presets-regexManagers/#regexmanagersbiomeversions

Example configuration

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": ["config:recommended", "regexManagers:biomeVersions"]
}

Code of Conduct

• I agree to follow Biome's Code of Conduct

Documentation URL

https://biomejs.dev/reference/cli/

Description

biome check and biome ci commands are quite similar, which could lead to confusion among users.

Expectations

To help clarify, it would be useful to explicitly describe the distinct use cases or benefits of each command. For example, indicating if biome ci command offers diagnostic outputs on GitHub would be particularly helpful. This would assist users in making more informed choices between the two commands.

Code of Conduct

• I agree to follow Biome's Code of Conduct

Documentation URL

https://biomejs.dev/linter/rules/use-import-extensions/

Description

make sure to enable allowImportingTsExtensions=true in your tsconfig.json.

This seems to be an incorrect statement, as allowImportingTsExtensions no longer is useful due to explicit extension mapping support, and it never was super useful to begin with, as it was blocking emission of transpiled code, so referring to it is more confusing than helpful.

Rule does not yet check filesystem for file type. It tries to guess which extension it should add based on the file extension of the current file and the import path.

Caveat seems both redundant and also confusing, having in mind that "Options" section explains both the default and the option to provide mapping manually, while caveat only refers to the default behaviour.

Expectations

Documentation doesn't contain redundant or confusing descriptions.

Code of Conduct

• I agree to follow Biome's Code of Conduct

Documentation URL

https://biomejs.dev/reference/cli

Description

I created PRs

• to add --write, --fix, --unsafe options to fixable commands.
• to deprecate --apply and --apply-unsafe options of biome <check|lint>

The website documentation should be updated for the change.

Expectations

The page should reflect the actual command options.

Code of Conduct

• I agree to follow Biome's Code of Conduct

Documentation URL

https://biomejs.dev/formatter/differences-with-prettier/

Description

Some documented differences with Prettier are no longer differences because Prettier's behavior changed in the meantime:

Prettier doesn’t unquote some object properties that are valid JavaScript identifiers

✔️ Still correct
Code example in Prettier Playground | Code example in Biome Playground

Prettier has an inconsistent behavior for assignment in computed keys.

✔️ Still correct
Code example in Prettier Playground | Code example in Biome Playground

Prettier adds a trailing comma to type parameters of arrow functions even when it is not required.

✔️ Still correct
Code example in Prettier Playground | Code example in Biome Playground

Prettier has an inconsistent behavior for parenthesized non-null-asserted optional chains

⚠️ Prettier throws an error now about the invalid syntax
Code example in Prettier Playground | Code example in Biome Playground

Prettier formats invalid syntaxes – Duplicate modifiers on class properties

⚠️ Prettier throws an error now about the invalid syntax
Code example in Prettier Playground | Code example in Biome Playground

Prettier formats invalid syntaxes – Assignment to an optional chain

✔️ Still correct
Code example in Prettier Playground | Code example in Biome Playground

Prettier formats invalid syntaxes – Incorrect modifier for the type parameters of an interface

✔️ Still correct
Code example in Prettier Playground | Code example in Biome Playground

Prettier formats invalid syntaxes – Top-level return

✔️ Still correct
Code example in Prettier Playground | Code example in Biome Playground

Prettier formats invalid syntaxes – Erroneous self-increment and self-decrement

⚠️ Prettier throws an error now about the invalid syntax
Code example in Prettier Playground | Code example in Biome Playground

Prettier formats invalid syntaxes – Use of abstract modifier in non-abstract classes

✔️ Still correct
Code example in Prettier Playground | Code example in Biome Playground

Prettier has inconsistencies between TypeScript and Babel parsing

⚠️ Prettier formats the code consistently now with the babel/babel-ts/typescript parsers
Code example in Prettier Playground | Code example in Biome Playground

Expectations

For all differences with a ✔️:

• These are fine, so nothing to change here.

For all differences with a ⚠️:

• Either the issue is fixed in Prettier completely, then there is no difference between Biome's and Prettier's behavior anymore, so the corresponding section should be removed from the docs.
• Or the issue is only partially fixed in Prettier (at least for the documented code example), but still persists for other code examples. Then the documentation should be updated to include a code example that actually highlights the difference between Biome's and Prettier's behavior.

Code of Conduct

• I agree to follow Biome's Code of Conduct

Documentation URL

https://biomejs.dev/guides/getting-started/

Description

The docs page looks a bit cluttered in portrait mode.

Expectations

It'd be nice if users could collapse the left-hand sidebar.

A keyboard shortcut like Ctrl + Shift + S to toggle the left-hand sidebar would be a nice feature, too.

Code of Conduct

• I agree to follow Biome's Code of Conduct

Documentation URL

https://biomejs.dev/linter/rules/use-valid-autocomplete

Description

When I click on the useValidAutocomplete link from the https://biomejs.dev/ja/linter/rules-sources/#eslint-plugin-jsx-a11y page, I get a 404.

Expectations

It seems that the rule has already been added in feat(lint/useValidAutocomplete): add rule, so use-valid-autocomplet.md file and documentation should be created.

Code of Conduct

• I agree to follow Biome's Code of Conduct

Documentation URL

https://biomejs.dev/linter/#rules

Description

The documentation page for the noDebugger rule currently links to a local development environment URL. This link should be relative instead of absolute

Wrong link: http://localhost:4321/linter/rules/no-debugger

Expectations

Expectations

The link in the Linter Rules documentation should be a relative path, ensuring it is functional regardless of the environment in which the documentation is viewed.

Expected link: https://biomejs.dev/linter/rules/no-debugger/

Code of Conduct

• I agree to follow Biome's Code of Conduct

Documentation URL

https://biomejs.dev/linter/rules/no-dangerously-set-inner-html
https://biomejs.dev/linter/rules/no-dangerously-set-inner-html-with-children

Description

Those two have switched the ESLint rule they refer to. It should say that rule lint/security/noDangerouslySetInnerHtml is the same as react/no-danger, and rule lint/security/noDangerouslySetInnerHtmlWithChildren is the same as react/no-danger-with-children

Expectations

Lint descriptions match the ESLint rules.

Code of Conduct

• I agree to follow Biome's Code of Conduct

Add a CODEOWNERS file to reference language specific teams