Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Snyk] Upgrade @biomejs/biome from 1.8.3 to 2.2.2 #389

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Upgrade @biomejs/biome from 1.8.3 to 2.2.2 #389

wants to merge 1 commit into from

Conversation

nerdy-tech-com-gitub
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade @biomejs/biome from 1.8.3 to 2.2.2.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

  • The recommended version is 37 versions ahead of your current version.

  • The recommended version was released 23 days ago.

Release notes
Package name: @biomejs/biome
  • 2.2.2 - 2025-08-23

    2.2.2

    Patch Changes

    • #7266 b270bb5 Thanks @ ematipico! - Fixed an issue where Biome got stuck when analyzing some files. This is usually caused by a bug in the inference engine. Now Biome has some guards in place in case the number of types grows too much, and if that happens, a diagnostic is emitted and the inference is halted.

    • #7281 6436180 Thanks @ ematipico! - Fixed an issue where the function scanProject wouldn't work as expected.

    • #7285 1511d0c Thanks @ rriski! - Partially fixed #6782: JSX node kinds are now supported in GritQL AST nodes.

    • #7249 dff85c0 Thanks @ ematipico! - Fixed #748, where Biome Language Server didn't show the unsafe fixes when requesting the quick fixes. Now all LSP editors will show also opt-in, unsafe fixes.

    • #7266 b270bb5 Thanks @ ematipico! - Fixed #7020: Resolved an issue with analysing types of static member expressions involving unions. If the object type was a union that referenced nested unions, it would trigger an infinite loop as it tried to keep expanding nested unions, and the set of types would grow indefinitely.

    • #7209 679b70e Thanks @ patrickshipe! - Resolved an overcorrection in useImportExtensions when importing explicit index files.

      Imports that explicitly reference an index file are now preserved and no longer rewritten to nested index paths.

      Example

      - import "./sub/index";
      + import "./sub/index/index.js";

      // After
      - import "./sub/index";
      + import "./sub/index.js";

    • #7270 953f9c6 Thanks @ arendjr! - Fixed #6172: Resolved an issue with inferring types for rest parameters. This issue caused rest-parameter types to be incorrect, and in some cases caused extreme performance regressions in files that contained many methods with rest-parameter definitions.

    • #7234 b7aa111 Thanks @ JeetuSuthar! - Fixed #7233: The useIndexOf rule now correctly suggests using indexOf() instead of findIndex().

      The diagnostic message was incorrectly recommending Array#findIndex() over Array#indexOf(), when it should recommend the opposite for simple equality checks.

    • #7283 0b07f45 Thanks @ ematipico! - Fixed #7236. Now Biome correctly migrates JSONC configuration files when they are passed using --config-path.

    • #7239 1d643d8 Thanks @ minht11! - Fixed an issue where Svelte globals ($state and so on) were not properly recognized inside .svelte.test.ts/js and .svelte.spec.ts/js files.

    • #7264 62fdbc8 Thanks @ ematipico! - Fixed a regression where when using --log-kind-pretty wasn't working anymore as expected.

    • #7244 660031b Thanks @ JeetuSuthar! - Fixed #7225: The noExtraBooleanCast rule now preserves parentheses when removing Boolean calls inside negations.

      // Before
!Boolean(b0 && b1);
// After
!(b0 && b1); // instead of !b0 && b1

    • #7298 46a8e93 Thanks @ unvalley! - Fixed #6695: useNamingConvention now correctly reports TypeScript parameter properties with modifiers.

      Previously, constructor parameter properties with modifiers like private or readonly were not checked against naming conventions. These properties are now treated consistently with regular class properties.

    What's Changed

    New Contributors

    Full Changelog: https://github.com/biomejs/biome/compare/@ biomejs/[email protected]...@ biomejs/[email protected]

  • 2.2.0 - 2025-08-14

    2.2.0

    Minor Changes

    • #5506 1f8755b Thanks @ sakai-ast! - The noRestrictedImports rule has been enhanced with a new patterns option. This option allows for more flexible and powerful import restrictions using gitignore-style patterns.

      You can now define patterns to restrict entire groups of modules. For example, you can disallow imports from any path under import-foo/ except for import-foo/baz.

      {
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*", "!import-foo/baz"],
        "message": "import-foo is deprecated, except for modules in import-foo/baz."
      }
    ]
  }
}

      Invalid examples

      import foo from "import-foo/foo";
import bar from "import-foo/bar";

      Valid examples

      import baz from "import-foo/baz";

      Additionally, the patterns option introduces importNamePattern to restrict specific import names using regular expressions.
      The following example restricts the import names that match x , y or z letters from modules under import-foo/.

      {
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*"],
        "importNamePattern": "[xyz]"
      }
    ]
  }
}

      Invalid examples

      import { x } from "import-foo/foo";

      Valid examples

      import { foo } from "import-foo/foo";

      Furthermore, you can use the invertImportNamePattern boolean option to reverse this logic. When set to true, only the import names that match the importNamePattern will be allowed. The following configuration only allows the import names that match x , y or z letters from modules under import-foo/.

      {
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*"],
        "importNamePattern": "[xyz]",
        "invertImportNamePattern": true
      }
    ]
  }
}

      Invalid examples

      import { foo } from "import-foo/foo";

      Valid examples

      import { x } from "import-foo/foo";

    • #6506 90c5d6b Thanks @ nazarhussain! - Allow customization of the sort order for different sorting actions. These actions now support a sort option:

      For each of these options, the supported values are the same:

      1. natural. Compares two strings using a natural ASCII order. Uppercase letters come first (e.g. A < a < B < b) and number are compared in a human way (e.g. 9 < 10). This is the default value.
      2. lexicographic. Strings are ordered lexicographically by their byte values. This orders Unicode code points based on their positions in the code charts. This is not necessarily the same as “alphabetical” order, which varies by language and locale.

    • #7159 df3afdf Thanks @ ematipico! - Added the new rule useBiomeIgnoreFolder. Since v2.2, Biome correctly prevents the indexing and crawling of folders.

      However, the correct pattern has changed. This rule attempts to detect incorrect usage, and promote the new pattern:

      // biome.json
{
  "files": {
    "includes": [
-      "!dist/**",
-      "!**/fixtures/**",
+      "!dist",
+      "!**/fixtures",
    ]
  }
}

    • #6989 85b1128 Thanks @ arendjr! - Fixed minor inconsistencies in how files.includes was being handled.

      Previously, Biome sometimes failed to properly ignore the contents of a folder if you didn't specify the /** at the end of a glob pattern. This was unfortunate, because it meant we still had to traverse the folder and then apply the glob to every entry inside it.

      This is no longer an issue and we now recommend to ignore folders without using the /** suffix.

    • #7118 a78e878 Thanks @ avshalomt2! - Added support for .graphqls files. Biome can now format and lint GraphQL files that have the extension .graphqls

    • #6159 f02a296 Thanks @ bavalpey! - Added a new option to Biome's JavaScript formatter, javascript.formatter.operatorLinebreak, to configure whether long lines should be broken before or after binary operators.

      For example, the following configuration:

      {
  formatter: {
    javascript: {
      operatorLinebreak: "before", // defaults to "after"
    },
  },
}

      Will cause this JavaScript file:

      const VERY_LONG_CONDITION_1234123412341234123412341234 = false;

      if (
      VERY_LONG_CONDITION_1234123412341234123412341234 &&
      VERY_LONG_CONDITION_1234123412341234123412341234 &&
      VERY_LONG_CONDITION_1234123412341234123412341234 &&
      VERY_LONG_CONDITION_1234123412341234123412341234
      ) {
      console.log("DONE");
      }

      to be formatted like this:

      const VERY_LONG_CONDITION_1234123412341234123412341234 = false;
if (
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234
) {
  console.log("DONE");
}

    • #7137 a653a0f Thanks @ ematipico! - Promoted multiple lint rules from nursery to stable groups and renamed several rules for consistency.

      Promoted rules

      The following rules have been promoted from nursery to stable groups:

      CSS
      GraphQL
      JavaScript/TypeScript

      Renamed rules

      The following rules have been renamed during promotion. The migration tool will automatically update your configuration:

      Configuration files using the old rule names will need to be updated. Use the migration tool to automatically update your configuration:

      biome migrate --write

    • #7159 df3afdf Thanks @ ematipico! - Added the new rule noBiomeFirstException. This rule prevents the incorrect usage of patterns inside files.includes.

      This rule catches if the first element of the array contains !. This mistake will cause Biome to analyze no files:

      // biome.json
{
  files: {
    includes: ["!dist/**"], // this is an error
  },
}

    • #6923 0589f08 Thanks @ ptkagori! - Added Qwik Domain to Biome

      This release introduces Qwik domain support in Biome, enabling Qwik developers to use Biome as a linter and formatter for their projects.

    • #6989 85b1128 Thanks @ arendjr! - Fixed #6965: Implemented smarter scanner for project rules.

      Previously, if project rules were enabled, Biome's scanner would scan all dependencies regardless of whether they were used by/reachable from source files or not. While this worked for a first version, it was far from optimal.

      The new scanner first scans everything listed under the files.includes setting, and then descends into the dependencies that were discovered there, including transitive dependencies. This has three main advantages:

      • Dependencies that are not reachable from your source files don't get indexed.
      • Dependencies that have multiple type definitions, such as those with separate definitions for CommonJS and ESM imports, only have the relevant definitions indexed.
      • If vcs.useIgnoreFile is enabled, .gitignore gets respected as well. Assuming you have folders such as build/ or dist/ configured there, those will be automatically ignored by the scanner.

      The change in the scanner also has a more nuanced impact: Previously, if you used files.includes to ignore a file in an included folder, the scanner would still index this file. Now the file is fully ignored, unless you import it.

      As a user you should notice better scanner performance (if you have project rules enabled), and hopefully you need to worry less about configuring files.experimentalScannerIgnores. Eventually our goal is still to deprecate that setting, so if you're using it today, we encourage you to see which ignores are still necessary there, and whether you can achieve the same effect by ignoring paths using files.includes instead.

      None of these changes affect the scanner if no project rules are enabled.

    • #6731 d6a05b5 Thanks @ ematipico! - The --reporter=summary has been greatly enhanced. It now shows the list of files that contains violations, the files shown are clickable and can be opened from the editor.

      Below an example of the new version:

@snyk-bot
feat: upgrade @biomejs/biome from 1.8.3 to 2.2.2
d71a129 
Snyk has created this PR to upgrade @biomejs/biome from 1.8.3 to 2.2.2.

See this package in npm:
@biomejs/biome

See this project in Snyk:
https://app.snyk.io/org/nerds-github/project/5d563373-8b29-4868-a93c-4cf8edeb3642?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@nerdy-tech-com-gitub @snyk-bot