Bump @biomejs/wasm-nodejs from 1.8.3 to 1.9.0

[dependabot]

Bumps @biomejs/wasm-nodejs from 1.8.3 to 1.9.0.

Release notes

Sourced from @​biomejs/wasm-nodejs's releases.

CLI v1.9.0

Analyzer

• Implement the semantic model for CSS. Contributed by @​togami2864

CLI

New features

• Add --graphql-linter-enabled option, to control whether the linter should be enabled or not for GraphQL files. Contributed by @​ematipico

• New EXPERIMENTAL search command. The search command allows you to search a Biome project using GritQL syntax.

  GritQL is a powerful language that lets you do structural searches on your codebase. This means that trivia such as whitespace or even the type of strings quotes used will be ignored in your search query. It also has many features for querying the structure of your code, making it much more elegant for searching code than regular expressions.

  While we believe this command may already be useful to users in some situations (especially when integrated in the IDE extensions!), we also had an ulterior motive for adding this command: We intend to utilize GritQL for our plugin efforts, and by allowing our users to try it out in a first iteration, we hope to gain insight in the type of queries you want to do, as well as the bugs we need to focus on.

  For now, the search command is explicitly marked as EXPERIMENTAL, since many bugs remain. Keep this in mind when you try it out, and please let us know your issues!

  Note: GritQL escapes code snippets using backticks, but most shells interpret backticks as command invocations. To avoid this, it's best to put single quotes around your Grit queries.

  biome search '`console.log($message)`' # find all `console.log` invocations

  Contributed by @​arendjr and @​BackupMiles

• The option --max-diagnostics now accept a none value, which lifts the limit of diagnostics shown. Contributed by @​ematipico

  • Add a new reporter --reporter=gitlab, that emits diagnostics for using the GitLab Code Quality report.

    [
      {
        "description": "Use === instead of ==. == is only allowed when comparing against `null`",
        "check_name": "lint/suspicious/noDoubleEquals",
        "fingerprint": "6143155163249580709",
        "severity": "critical",
        "location": {
          "path": "main.ts",
          "lines": {
            "begin": 4
          }
        }
      }
    ]

    Contributed by @​NiclasvanEyk

... (truncated)

Changelog

Sourced from @​biomejs/wasm-nodejs's changelog.

v1.9.0 (2024-09-12)

Analyzer

• Implement the semantic model for CSS. Contributed by @​togami2864

CLI

New features

• Add --graphql-linter-enabled option, to control whether the linter should be enabled or not for GraphQL files. Contributed by @​ematipico

• New EXPERIMENTAL search command. The search command allows you to search a Biome project using GritQL syntax.

  GritQL is a powerful language that lets you do structural searches on your codebase. This means that trivia such as whitespace or even the type of strings quotes used will be ignored in your search query. It also has many features for querying the structure of your code, making it much more elegant for searching code than regular expressions.

  While we believe this command may already be useful to users in some situations (especially when integrated in the IDE extensions!), we also had an ulterior motive for adding this command: We intend to utilize GritQL for our plugin efforts, and by allowing our users to try it out in a first iteration, we hope to gain insight in the type of queries you want to do, as well as the bugs we need to focus on.

  For now, the search command is explicitly marked as EXPERIMENTAL, since many bugs remain. Keep this in mind when you try it out, and please let us know your issues!

  Note: GritQL escapes code snippets using backticks, but most shells interpret backticks as command invocations. To avoid this, it's best to put single quotes around your Grit queries.

  biome search '`console.log($message)`' # find all `console.log` invocations

  Contributed by @​arendjr and @​BackupMiles

• The option --max-diagnostics now accept a none value, which lifts the limit of diagnostics shown. Contributed by @​ematipico

  • Add a new reporter --reporter=gitlab, that emits diagnostics for using the GitLab Code Quality report.

    [
      {
        "description": "Use === instead of ==. == is only allowed when comparing against `null`",
        "check_name": "lint/suspicious/noDoubleEquals",
        "fingerprint": "6143155163249580709",
        "severity": "critical",
        "location": {
          "path": "main.ts",
          "lines": {
            "begin": 4
          }
        }
      }
    ]

    Contributed by @​NiclasvanEyk

... (truncated)

Commits

• b260d5b feat(package.json): set version to 1.9
• b7c67fc revert(package.json): version
• 894c3c5 release: v1.9.0 (#3794)
• 9c9a599 chore: add additional debug logs for #3839 (#3855)
• dc2122e fix: optional ARIA properties for role="separator" in useAriaPropsForRole...
• 39a820e fix(parser/html): correctly lex tag names and attribute names (#3853)
• 83e5cef ci: fix check deps error (#3851)
• e135108 chore: add vohoanglong0107 as maintainer (#3849)
• 7ffc53f refactor(changelog): add missing entries, order existing ones (#3847)
• 647653a feat(parser/html): emit diagnostics for parsing errors (#3846)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)