Version History

Version 2.1.2

Patch Changes

#6865 b35bf64 Thanks @denbezrukov! - Fix #6485: Handle multiple semicolons correctly in blocks (#6485)
```
1
div {
2
  box-sizing: border-box;
3
  color: red;
4
}
```
#6798 3579ffa Thanks @dyc3! - Fixed #6762, Biome now knows that ~/.config/zed/settings.json and ~/.config/Code/User/settings.json allows comments by default.
#6839 4cd62d8 Thanks @ematipico! - Fixed #6838, where the Biome File Watcher incorrectly watched and stored ignored files, causing possible memory leaks when those files were dynamically created (e.g. built files).
#6879 0059cd9 Thanks @denbezrukov! - Refactor: remove one level of indirection for CSS declarations with semicolon Previously, accessing a declaration from a list required an extra step:
```
1
item
2
.as_any_css_declaration_with_semicolon()
3
.as_css_declaration_with_semicolon()
```
Now, it can be done directly with:
```
1
item.as_css_declaration_with_semicolon()
```
#6839 4cd62d8 Thanks @ematipico! - Fixed a bug where the Biome Language Server didn’t correctly ignore specific files when vcs.useIgnoreFile is set to true.
#6884 5ff50f8 Thanks @arendjr! - Improved the performance of noImportCycles by ~30%.
#6903 241dd9e Thanks @arendjr! - Fixed #6829: Fixed a false positive reported by useImportExtensions when importing a .js file that had a matching .d.ts file in the same folder.
#6846 446112e Thanks @darricheng! - Fixed an issue where biome was using the wrong string quotes when the classes string has quotes, resulting in invalid code after applying the fix.
#6823 eebc48e Thanks @arendjr! - Improved #6172: Optimised the way function arguments are stored in Biome’s type inference. This led to about 10% performance improvement in RedisCommander.d.ts and about 2% on @next/font type definitions.
#6878 3402976 Thanks @ematipico! - Fixed a bug where the Biome Language Server would apply an unsafe fix when using the code action quickfix.biome.

Now Biome no longer applies an unsafe code fix when using the code action quickfix.biome.

#6794 4d5fc0e Thanks @vladimir-ivanov! - Fixed #6719: The noInvalidUseBeforeDeclaration rule covers additional use cases.

Examples:

1
type Bar = { [BAR]: true };
2
const BAR = "bar";

1
interface Bar {
2
  child: { grandChild: { [BAR]: typeof BAR; enumFoo: EnumFoo } };
3
}
4
const BAR = "bar";
5
enum EnumFoo {
6
  BAR = "bar",
7
}

#6863 531e97e Thanks @dyc3! - Biome now considers whether the linter is enabled when figuring out how the project should be scanned. Resolves #6815.
#6832 bdbc2b1 Thanks @togami2864! - Fixed #6165: Fixed false negative in noUnusedPrivateClassMembers rule when checking member usage in classes
#6839 4cd62d8 Thanks @ematipico! - Fixed a bug where the root ignore file wasn’t correctly loaded during the scanning phase, causing false positives and incorrect expectations among users.

Now, when using vcs.useIgnoreFile, the **the globs specified in the ignore file from the project root ** will have the same semantics as the files.includes setting of the root configuration.

Refer to the relative web page to understand how they work.
#6898 5beb024 Thanks @arendjr! - Fixed #6891: Improved type inference for array indices.

Example:
```
1
const numbers: number[];
2
numbers[42]; // This now infers to `number | undefined`.
```

#6809 8192451 Thanks @arendjr! - Fixed #6796: Fixed a false positive that happened in noFloatingPromises when calling functions that were declared as part of for ... of syntax inside async functions.

Instead, the variables declared inside for ... of loops are now correctly inferred if the expression being iterated evaluates to an Array (support for other iterables will follow later).

Invalid example

1
const txStatements: Array<(tx) => Promise<any>> = [];
2

3
db.transaction((tx: any) => {
4
  for (const stmt of txStatements) {
5
    // We correctly flag this resolves to a `Promise`:
6
    stmt(tx);
7
  }
8
});

Valid example

1
async function valid(db) {
2
  const txStatements: Array<(tx: any) => void> = [(tx) => tx.insert().run()];
3

4
  db.transaction((tx: any) => {
5
    for (const stmt of txStatements) {
6
      // We don't flag a false positive here anymore:
7
      stmt(tx);
8
    }
9
  });
10
}

#6757 13a0818 Thanks @mdevils! - Added the rule noVueReservedProps, resolves #6309.

It prevents the use of reserved Vue prop names such as key and ref which can cause conflicts and unexpected behavior in Vue components.

Invalid example

1
import { defineComponent } from "vue";
2

3
export default defineComponent({
4
  props: ["ref", "key", "foo"],
5
});

1
<script setup>
2
defineProps({
3
  ref: String,
4
  key: String,
5
  foo: String,
6
});
7
</script>

Valid examples

1
import { defineComponent } from "vue";
2

3
export default defineComponent({
4
  props: ["foo"],
5
});

1
<script setup>
2
defineProps({ foo: String });
3
</script>

#6840 1a57b51 Thanks @denbezrukov! - Allow multiple identifiers in ::part() pseudo-element selector.
```
1
::part(first second) {
2
}
```
#6845 4fd44ec Thanks @arendjr! - Fixed #6510: The scanner no longer shows diagnostics on inaccessible files unless --verbose is used.
#6844 b7e2d4d Thanks @sterliakov! - Fixed #6837: Fixed regression with multiple consecutive line suppression comments using instances (like // biome-ignore lint/correctness/useExhaustiveDependencies(depName): reason).
#6818 5f3f5a6 Thanks @siketyan! - Fixed an issue where textDocument/codeAction in the LSP could respond with outdated text edits after the workspace watcher observed outdated changes to the file.
#6804 3e6ab16 Thanks @arendjr! - noFloatingPromises will no longer suggest to add await keyword inside synchronous callbacks nested inside async functions.
#6901 c9e969a Thanks @arendjr! - Fixed #6777: Fixed type inference handling of this to avoid infinite recursion.

Thanks to @sterliakov for the thorough investigation!

#6855 d1581c7 Thanks @vladimir-ivanov! - Fixed #6775: useReadonlyClassProperties now also captures mutations inside function arguments.

Example:

1
class Counter {
2
  private counter: number;
3
  count() {
4
    console.log(this.counter++);
5
    const counterString = `${this.counter++}`;
6
  }
7
}

#6839 4cd62d8 Thanks @ematipico! - Fixed a bug where Biome didn’t throw any error when vcs.useIgnoreFile is set to true, and there wasn’t any ignore file read. Now Biome correctly throws an error if no ignore files are found.
#6911 6d68074 Thanks @arendjr! - Fixed #6838: Reduce resource consumption in the Biome Language Server by using non-recursive filesystem watchers instead of recursive ones.

Watchers are responsible for notifying Biome of changes to files in the filesystem. We used to set up a single recursive watcher, but that meant that Biome would receive filesystem notifications for all files in your project, even for ignored folders such as build/ or dist/ folders.

With this patch, we set up non-recursive watchers only for the folders that are relevant to a project.

Related to this, we also solved an issue where incoming notifications were incorrectly filtered, causing ignored files to be processed and stored in our module graph anyway.