v2.1.3

Compare Source

Patch Changes

• #​7057 634a667 Thanks @​mdevils! - Added the rule noVueReservedKeys, which prevents the use of reserved Vue keys.

  It prevents the use of Vue reserved keys such as those starting with # @​biomejs/biome (like $el, $data, $props) and keys starting with _` in data properties, which can cause conflicts and unexpected behavior in Vue components.

  Invalid example

  <script>
  export default {
    data: {
      $el: "",
      _foo: "bar",
    },
  };
  </script>

  <script>
  export default {
    computed: {
      $data() {
        return this.someData;
      },
    },
  };
  </script>

  Valid examples

  <script>
  export default {
    data() {
      return {
        message: "Hello Vue!",
        count: 0,
      };
    },
  };
  </script>

  <script>
  export default {
    computed: {
      displayMessage() {
        return this.message;
      },
    },
  };
  </script>

• #​6941 734d708 Thanks @​JamBalaya56562! - Added @eslint-react/no-nested-component-definitions as a rule source for noNestedComponentDefinitions. Now it will get picked up by biome migrate --eslint.

• #​6463 0a16d54 Thanks @​JamBalaya56562! - Fixed a website link for the useComponentExportOnlyModules linter rule to point to the correct URL.

• #​6944 e53f2fe Thanks @​sterliakov! - Fixed #​6910: Biome now ignores type casts and assertions when evaluating numbers for noMagicNumbers rule.

• #​6991 476cd55 Thanks @​denbezrukov! - Fixed #​6973: Add support for parsing the :active-view-transition-type() pseudo-class

  :active-view-transition-type(first second) {
  }

• #​6992 0b1e194 Thanks @​ematipico! - Added a new JSON rule called noQuickfixBiome, which disallow the use of code action quickfix.biome inside code editor settings.

• #​6943 249306d Thanks @​JamBalaya56562! - Fixed @vitest/eslint-plugin source url.

• #​6947 4c7ed0f Thanks @​JamBalaya56562! - Fixed ESLint migration for the rule prefer-for from eslint-plugin-solid to Biome's useForComponent.

• #​6976 72ebadc Thanks @​siketyan! - Fixed #​6692: The rules noUnusedVariables and noUnusedFunctionParameters no longer cause an infinite loop when the suggested name is not applicable (e.g. the suggested name is already declared in the scope).

• #​6990 333f5d0 Thanks @​rvanlaarhoven! - Fixed the documentation URL for lint/correctness/noUnknownPseudoClass

• #​7000 4021165 Thanks @​harxki! - Fixed #​6795: noUnassignedVariables now correctly recognizes variables used in JSX ref attributes.

• #​7044 b091ddf Thanks @​ematipico! - Fixed #​6622, now the rule useSemanticElements works for JSX self-closing elements too.

• #​7014 c4864e8 Thanks @​siketyan! - Fixed #​6516: The biome migrate command no longer break the member list with trailing comments.

• #​6979 29cb6da Thanks @​unvalley! - Fixed #​6767: useSortedClasses now correctly removes leading and trailing whitespace in className.

  Previously, trailing spaces in className were not fully removed.

  // Think we have this code:
  <div className="text-sm font-bold            " />
  
  // Before: applied fix, but a trailing space was preserved
  <div className="font-bold text-sm " />
  
  // After: applied fix, trailing spaces removed
  <div className="font-bold text-sm" />

• #​7055 ee4828d Thanks @​dyc3! - Added the nursery rule useReactFunctionComponents. This rule enforces the preference to use function components instead of class components.

  Valid:

  function Foo() {
    return <div>Hello, world!</div>;
  }

  Invalid:

  class Foo extends React.Component {
    render() {
      return <div>Hello, world!</div>;
    }
  }

• #​6924 2d21be9 Thanks @​ematipico! - Fixed #​113, where the Biome Language Server didn't correctly update the diagnostics when the configuration file is modified in the editor. Now the diagnostics are correctly updated every time the configuration file is modified and saved.

• #​6931 e6b2380 Thanks @​arendjr! - Fixed #​6915: useHookAtTopLevel no longer hangs when rules call themselves recursively.

• #​7012 01c0ab4 Thanks @​siketyan! - Fixed #​5837: Invalid suppression comments such as biome-ignore-all-start or biome-ignore-all-end no longer causes a panic.

• #​6949 48462f8 Thanks @​fireairforce! - Support parse import defer(which is a stage3 proposal). The syntax look like this:

  import defer * as foo from "<specifier>";

• #​6938 5feb5a6 Thanks @​vladimir-ivanov! - Fixed #​6919 and #​6920:
  useReadonlyClassProperties now does checks for mutations in async class methods.

  Example:

  class Counter3 {
    private counter: number;
    async count() {
      this.counter = 1;
      const counterString = `${this.counter++}`;
    }
  }

• #​6942 cfda528 Thanks @​sterliakov! - Fixed #​6939. Biome now understands this binding in classes outside of methods.

v2.1.2

Compare Source

Patch Changes

• #​6908 d77eaff Thanks @​ematipico! - Fix #​6485: Handle multiple semicolons correctly in blocks (#​6485)

  div {
    box-sizing: border-box;
    color: red;
  }

• #​6908 d77eaff Thanks @​ematipico! - Fixed #​6762, Biome now knows that ~/.config/zed/settings.json and ~/.config/Code/User/settings.json allows comments by default.

• #​6908 d77eaff Thanks @​ematipico! - Refactor: remove one level of indirection for CSS declarations with semicolon
  Previously, accessing a declaration from a list required an extra step:

  item
  .as_any_css_declaration_with_semicolon()
  .as_css_declaration_with_semicolon()

  Now, it can be done directly with:

  item.as_css_declaration_with_semicolon()

• #​6908 d77eaff Thanks @​ematipico! - Fixed a bug where the Biome Language Server didn't correctly ignore specific files when vcs.useIgnoreFile is set to true.

• #​6908 d77eaff Thanks @​ematipico! - Improved the performance of noImportCycles by ~30%.

• #​6908 d77eaff Thanks @​ematipico! - 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.

• #​6908 d77eaff Thanks @​ematipico! - 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.

• #​6908 d77eaff Thanks @​ematipico! - 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.

• #​6908 d77eaff 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.

• #​6908 d77eaff Thanks @​ematipico! - Fixed #​6719: The noInvalidUseBeforeDeclaration rule covers additional use cases.

  Examples:

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

  interface Bar {
    child: { grandChild: { [BAR]: typeof BAR; enumFoo: EnumFoo } };
  }
  const BAR = "bar";
  enum EnumFoo {
    BAR = "bar",
  }

• #​6908 d77eaff Thanks @​ematipico! - Biome now considers whether the linter is enabled when figuring out how the project should be scanned. Resolves #​6815.

• #​6908 d77eaff Thanks @​ematipico! - Fixed #​6165: Fixed false negative in noUnusedPrivateClassMembers rule when checking member usage in classes

• #​6908 d77eaff 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.

• #​6908 d77eaff Thanks @​ematipico! - Fixed #​6891: Improved type inference for array indices.

  Example:

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

• #​6908 d77eaff Thanks @​ematipico! - 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

  const txStatements: Array<(tx) => Promise<any>> = [];
  
  db.transaction((tx: any) => {
    for (const stmt of txStatements) {
      // We correctly flag this resolves to a `Promise`:
      stmt(tx);
    }
  });

  Valid example

  async function valid(db) {
    const txStatements: Array<(tx: any) => void> = [(tx) => tx.insert().run()];
  
    db.transaction((tx: any) => {
      for (const stmt of txStatements) {
        // We don't flag a false positive here anymore:
        stmt(tx);
      }
    });
  }

• #​6908 d77eaff Thanks @​ematipico! - 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

  import { defineComponent } from "vue";
  
  export default defineComponent({
    props: ["ref", "key", "foo"],
  });

  <script setup>
  defineProps({
    ref: String,
    key: String,
    foo: String,
  });
  </script>

  Valid examples

  import { defineComponent } from "vue";
  
  export default defineComponent({
    props: ["foo"],
  });

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

• #​6912 af7c6c0 Thanks @​ematipico! - Fixed #​6904. Now Biome correctly applies the argument --assist-enabled=false when running the command ci and the command check.

• #​6908 d77eaff Thanks @​ematipico! - Allow multiple identifiers in ::part() pseudo-element selector.

  ::part(first second) {
  }

• #​6908 d77eaff Thanks @​ematipico! - Fixed #​6510: The scanner no longer shows diagnostics on inaccessible files unless --verbose is used.

• #​6908 d77eaff Thanks @​ematipico! - Fixed #​6837: Fixed regression with multiple consecutive line suppression comments using instances (like // biome-ignore lint/correctness/useExhaustiveDependencies(depName): reason).

• #​6908 d77eaff Thanks @​ematipico! - 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.

• #​6908 d77eaff Thanks @​ematipico! - noFloatingPromises will no longer suggest to add await keyword inside synchronous callbacks nested inside async functions.

• #​6908 d77eaff Thanks @​ematipico! - Fixed #​6777: Fixed type inference handling of this to avoid infinite recursion.

  Thanks to @​sterliakov for the thorough investigation!

• #​6908 d77eaff Thanks @​ematipico! - Fixed #​6775: useReadonlyClassProperties now also captures mutations inside function arguments.

  Example:

  class Counter {
    private counter: number;
    count() {
      console.log(this.counter++);
      const counterString = `${this.counter++}`;
    }
  }

• #​6723 c434f01 Thanks @​sterliakov! - useUniqueElementIds now has an excludedComponents option to support elements using id prop for reasons not related to DOM element id. Fixed #​6722.

• #​6908 d77eaff 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.