変更履歴

All versions

Version 2.4.10 Latest

Patch Changes

#8838 f3a6a6b Thanks @baeseokjae! - Added new lint nursery rule noImpliedEval.

The rule detects implied eval() usage through functions like setTimeout, setInterval, and setImmediate when called with string arguments.
```
1
// Invalid
2
setTimeout("alert('Hello');", 100);
3

4
// Valid
5
setTimeout(() => alert("Hello"), 100);
```
#9320 93c3b6c Thanks @taberoajorge! - Fixed #7664: noUnusedVariables no longer reports false positives for TypeScript namespace declarations that participate in declaration merging with an exported or used value declaration (const, function, or class) of the same name. The reverse direction is also handled: a value declaration merged with an exported namespace is no longer flagged.
#9630 1dd4a56 Thanks @raashish1601! - Fixed #9629: noNegationElse now keeps ternary branch comments attached to the correct branch when applying its fixer.
#9216 04243b0 Thanks @FrederickStempfle! - Fixed #9061: noProcessEnv now also detects process.env when process is imported from the "process" or "node:process" modules.

Previously, only the global process object was flagged:
```
1
import process from "node:process";
2
// This was not flagged, but now it is:
3
console.log(process.env.NODE_ENV);
```
#9692 61b7ec5 Thanks @mkosei! - Fixed Svelte #each destructuring parsing and formatting for nested patterns such as [key, { a, b }].
#9627 06a0f35 Thanks @ematipico! - Fixed #191: Improved the performance of how the Biome Language Server pulls code actions and diagnostics.

Before, code actions were pulled and computed all at once in one request. This approach couldn’t work in big files, and caused Biome to stale and have CPU usage spikes up to 100%.

Now, code actions are pulled and computed lazily, and Biome won’t choke anymore in big files.
#9643 5bfee36 Thanks @dyc3! - Fixed #9347: useVueValidVBind no longer reports valid object bindings like v-bind="props".
#9627 06a0f35 Thanks @ematipico! - Fixed assist diagnostics being invisible when using --diagnostic-level=error. Enforced assist violations (e.g. useSortedKeys) were filtered out before being promoted to errors, causing biome check to incorrectly return success.
#9695 9856a87 Thanks @dyc3! - Added the new nursery rule noUnsafePlusOperands, which reports + and += operations that use object-like, symbol, unknown, or never operands, or that mix number with bigint.
#9627 06a0f35 Thanks @ematipico! - Fixed duplicate parse errors in check and ci output. When a file had syntax errors, the same parse error was printed twice and the error count was inflated.
#9627 06a0f35 Thanks @ematipico! - Improved the performance of the commands lint and check when they are called with --write.
#9627 06a0f35 Thanks @ematipico! - Fixed --diagnostic-level not fully filtering diagnostics. Setting --diagnostic-level=error now correctly excludes warnings and infos from both the output and the summary counts.
#9623 13b3261 Thanks @ematipico! - Fixed #9258: --skip no longer causes suppressions/unused warnings for suppression comments targeting skipped rules or domains.
#9631 599dd04 Thanks @raashish1601! - Fixed #9625: experimentalEmbeddedSnippetsEnabled no longer crashes when a file mixes formatable CSS-in-JS templates with tagged templates that the embedded formatter can’t currently delegate, such as a styled-components interpolation returning `css```.