Skip to content
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.

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

chore(deps): update dependencies (non-major) #147

Merged
merged 1 commit into from
Oct 5, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 9, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@astrojs/check (source) ^0.9.3 -> ^0.9.4 age adoption passing confidence
@biomejs/biome (source) 1.8.3 -> 1.9.3 age adoption passing confidence
@changesets/cli (source) 2.27.7 -> 2.27.9 age adoption passing confidence
@floating-ui/dom (source) ^1.6.10 -> ^1.6.11 age adoption passing confidence
@ocavue/eslint-config ^2.6.0 -> ^2.8.1 age adoption passing confidence
@types/bun (source) ^1.1.8 -> ^1.1.10 age adoption passing confidence
@vitest/browser (source) ^2.0.5 -> ^2.1.2 age adoption passing confidence
@zag-js/dismissable ^0.65.1 -> ^0.73.1 age adoption passing confidence
@zag-js/dom-query ^0.65.1 -> ^0.73.1 age adoption passing confidence
astro (source) ^4.15.1 -> ^4.15.11 age adoption passing confidence
astrobook ^0.4.2 -> ^0.4.4 age adoption passing confidence
eslint (source) ^9.9.1 -> ^9.12.0 age adoption passing confidence
lefthook 1.7.15 -> 1.7.18 age adoption passing confidence
pkg-pr-new (source) ^0.0.24 -> ^0.0.29 age adoption passing confidence
playwright (source) ^1.46.1 -> ^1.47.2 age adoption passing confidence
pnpm (source) 9.9.0 -> 9.12.0 age adoption passing confidence
tsup (source) ^8.2.4 -> ^8.3.0 age adoption passing confidence
turbo (source) 2.1.1 -> 2.1.3 age adoption passing confidence
typedoc (source) 0.26.7 -> 0.26.8 age adoption passing confidence
typescript (source) ^5.5.4 -> ^5.6.2 age adoption passing confidence
vitest (source) ^2.0.5 -> ^2.1.2 age adoption passing confidence

Release Notes

withastro/language-tools (@​astrojs/check)

v0.9.4

Compare Source

Patch Changes
biomejs/biome (@​biomejs/biome)

v1.9.3

Compare Source

CLI
New features
  • GritQL queries that match functions or methods will now match async functions or methods as well.

    If this is not what you want, you can capture the async keyword (or its absence) in a metavariable and assert its emptiness:

    $async function foo() {} where $async <: .
    

    Contributed by @​arendjr

Bug fixes
  • Fix #​4077: Grit queries no longer need to match the statement's trailing semicolon. Contributed by @​arendjr

  • Fix #​4102. Now the CLI command lint doesn't exit with an error code when using --write/--fix. Contributed by @​ematipico

Configuration
Bug fixes
  • Fix #​4125, where noLabelWithoutControl options where incorrectly marked as mandatory. Contributed by @​ematipico
Editors
  • Fix a case where CSS files weren't correctly linted using the default configuration. Contributed by @​ematipico
Formatter
Bug fixes
  • Fix #​3924 where GraphQL formatter panics in block comments with empty line. Contributed by @​vohoanglong0107

  • Fix a case where raw values inside url() functions weren't properly trimmed.

    .value {
    -  background: url(
    -   whitespace-around-string
    -  );
    + background: url(whitespace-around-string);
    }

    Contributed by @​ematipico

  • Fixed #​4076, where a media query wasn't correctly formatted:

    .class {
    -  @&#8203;media (1024px <= width <=1280px) {
    +  @&#8203;media (1024px <= width <= 1280px) {
       color: red;
       }
    }

    Contributed by @​blaze-d83

JavaScript API
Bug fixes
Linter
New features
Bug fixes
Parser
Bug fixes
  • Forbid undefined as type name for typescript parser. Contributed by @​fireairforce

v1.9.2

Compare Source

CLI
New features
Bug fixes
  • Fix #​3917, where the fixed files were incorrectly computed. Contributed by @​ematipico
  • Fixed an issue that caused GritQL contains queries to report false positives when the matched
    node appeared inside a sibling node. Contributed by @​arendjr
Editors
Bug fixes
  • Fix #​3923. Now the .editorconfig is correctly parsed by the LSP, and the options are correctly applied to files when formatting is triggered.
    Plus, the Biome LSP now watches for any change to the .editorconfig, and updates the formatting settings.

  • Reduced the number of log files generated by the LSP server. Now the maximum number of logs saved on disk is seven. Contributed by @​ematipico

  • Fix the code actions capabilities available in the LSP Biome server. Before, the LSP was using the default capabilities, which resulted in pulling code actions even when they were disabled by the editor.

    This means that the code actions are pulled by the client only when the editor enables quickfix.biome, source.organizeImports.biome and source.fixAll.biome.

    Now, if you enable organizeImports.enabled: true in the biome.json, and then you configure your editor with the following code action source.organizeImports.biome: false, the editor won't sort the imports.

    Contributed by @​ematipico

Linter
New features
Bug fixes
Parser
Bug fixes
  • useStrictMode now reports Script files with some directives, but without the use strict directive. Contributed by @​Conaclos

  • The CSS parser now accepts the characters U+FFDCF and U+FFFD in identifiers. Contributed by @​Conaclos

v1.9.1

Compare Source

Analyzer
CLI
Bug fixes
  • useEditorConfig now loads the editorconfig when running biome ci #​3864. Contributed by @​dyc3

  • Revert #​3731 to fix broken quick fixes and code actions. Contributed by @​nhedger

Configuration
Editors
Formatter
JavaScript APIs
Linter
New Features
Bug fixes
Parser

v1.9.0

Compare Source

Analyzer
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

  • Add new options to the lsp-proxy and start commands:

    • --log-path: a directory where to store the daemon logs. The commands also accepts the environment variable BIOME_LOG_PATH.
    • --log-prefix-name: a prefix that's added to the file name of the logs. It defaults to server.log. The commands also accepts the environment variable BIOME_LOG_PREFIX_NAME.

    @​Contributed by @​ematipico

Enhancements
  • When a --reporter is provided, and it's different from the default one, the value provided by via --max-diagnostics is ignored and the limit is lifted. Contributed by @​ematipico

  • biome init now generates a new config file with more options set.
    This change intends to improve discoverability of the options and to set the more commonly used options to their default values.
    Contributed by @​Conaclos

  • The --verbose flag now reports the list of files that were evaluated, and the list of files that were fixed.
    The evaluated files are the those files that can be handled by Biome, files that are ignored, don't have an extension or have an extension that Biome can't evaluate are excluded by this list.
    The fixed files are those files that were handled by Biome and changed. Files that stays the same after the process are excluded from this list.

     VERBOSE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    
      ℹ Files processed:
    
      - biome/biome.json
      - biome/packages/@&#8203;biomejs/cli-win32-arm64/package.json
      - biome/packages/tailwindcss-config-analyzer/package.json
    
     VERBOSE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    
      ℹ Files fixed:
    
      - biome/biome/packages/tailwindcss-config-analyzer/src/generate-tailwind-preset.ts

    Contributed by @​ematipico

  • Allow passing nursery to the --only and --skip filters.

    The --only option allows you to run a given rule or rule group.
    The --skip option allows you to skip the execution of a given group or a given rule.

    Previously, it was not possible to pass nursery.
    This restriction is now removed, as it may make sense to skip the nursery rules that a project has enabled.

    Contributed by @​Conaclos

  • The CLI now returns an error code when calling a command in stdin mode, and the contents of the files aren't fixed. For example, the following example will result in an error code of 1 because the lint command triggers some lint rules:

    echo "let x = 1" | biome lint --stdin-file-path=stdin.js

    Contributed by @​ematipico

Bug fixes
  • biome lint --write now takes --only and --skip into account (#​3470). Contributed by @​Conaclos

  • Fix #​3368, now the reporter github tracks the diagnostics that belong to formatting and organize imports. Contributed by @​ematipico

  • Fix #​3545, display a warning, 'Avoid using unnecessary Fragment,' when a Fragment contains only one child element that is placed on a new line. Contributed by @​satojin219

  • Migrating from Prettier or ESLint no longer overwrite the overrides field from the configuration (#​3544). Contributed by @​Conaclos

  • Fix JSX expressions for noAriaHiddenOnFocusable (#​3708). Contributed by @​anthonyshew

  • Fix edge case for <canvas> elements that use role="img" (#​3728). Contributed by @​anthonyshew

  • Fix #​3633, where diagnostics where incorrectly printed if the code has errors. Contributed by @​ematipico

  • Allow aria-label on heading to prevent useHeadingContent diagnostic (#​3767). Contributed by @​anthonyshew

  • Fix edge case #​3791 for rule noFocusedTests being used with non-string-like expressions (#​3793). Contributed by @​h-a-n-a

  • Fix optional ARIA properties for role="separator" in useAriaPropsForRole (#​3856). Contributed by @​anthonyshew

Configuration
  • Add support for loading configuration from .editorconfig files (#​1724).

    Configuration supplied in .editorconfig will be overridden by the configuration in biome.json. Support is disabled by default and can be enabled by adding the following to your formatter configuration in biome.json:

    {
      "formatter": {
        "useEditorconfig": true
      }
    }

    Contributed by @​dyc3

  • overrides from an extended configuration is now merged with the overrides of the extension.

    Given the following shared configuration biome.shared.json:

    {
      "overrides": [
        {
          "include": ["**/*.json"],
          // ...
        }
      ]
    }

    and the following configuration:

    {
      "extends": ["./biome.shared.json"],
      "overrides": [
        {
          "include": ["**/*.ts"],
          // ...
        }
      ]
    }

    Previously, the overrides from biome.shared.json was overwritten.
    It is now merged and results in the following configuration:

    {
      "extends": ["./biome.shared.json"],
      "overrides": [
        {
          "include": ["**/*.json"],
          // ...
        },
        {
          "include": ["**/*.ts"],
          // ...
        }
      ]
    }

    Contributed by @​Conaclos

Editors
  • Fix #​3577, where the update of the configuration file was resulting in the creation of a new internal project. Contributed by @​ematipico

  • Fix #​3696, where biome.jsonc was incorrectly parsed with incorrect options. Contributed by @​ematipico

Formatter
  • The CSS formatter is enabled by default. Which means that you don't need to opt-in anymore using the configuration file biome.json:

    {
    -  "css": {
    -    "formatter": {
    -      "enabled": true
    -    }
    -  }
    }

    Contributed by @​ematipico

  • Add parentheses for nullcoalescing in ternaries.

    This change aligns on Prettier 3.3.3.
    This adds clarity to operator precedence.

    - foo ? bar ?? foo : baz;
    + foo ? (bar ?? foo) : baz;

    Contributed by @​Conaclos

  • Keep the parentheses around infer ... extends declarations in type unions and type intersections (#​3419). Contributed by @​Conaclos

  • Keep parentheses around a yield expression inside a type assertion.

    Previously, Biome removed parentheses around some expressions that require them inside a type assertion.
    For example, in the following code, Biome now preserves the parentheses.

    function* f() {
      return <T>(yield 0);
    }

    Contributed by @​Conaclos

  • Remove parentheses around expressions that don't need them inside a decorator.

    Biome now matches Prettier in the following cases:

      class {
    -   @&#8203;(decorator)
    +   @&#8203;decorator
        method() {}
      },
      class {
    -   @&#8203;(decorator())
    +   @&#8203;decorator()
        method() {}
      },
      class {
        @&#8203;(decorator?.())
        method() {}
      },

    Contributed by @​Conaclos

  • Keep parentheses around objects preceded with a @satisfies comment.

    In the following example, parentheses are no longer removed.

    export const PROPS = /** @&#8203;satisfies {Record<string, string>} */ ({
      prop: 0,
    });

    Contributed by @​Conaclos

Linter
Promoted rules

New rules are incubated in the nursery group.
Once stable, we promote them to a stable group.

The following CSS rules are promoted:

The following JavaScript rules are promoted:

Deprecated rules
New features
Enhancements
  • Rename nursery/noUnknownSelectorPseudoElement to nursery/noUnknownPseudoElement. Contributed by @​togami2864

  • The CSS linter is now enabled by default. Which means that you don't need to opt-in anymore using the configuration file biome.json:

    {
    -  "css": {
    -    "linter": {
    -      "enabled": true
    -    }
    -  }
    }

    Contributed by @​ematipico

  • The JavaScript linter recognizes TypeScript 5.5 and 5.6 globals. Contributed by @​Conaclos

  • noBlankTarget now supports an array of allowed domains.

    The following configuration allows example.com and example.org as blank targets.

    "linter": {
      "rules": {
        "a11y": {
          "noBlankTarget": {
          "level": "error",
            "options": {
               "allowDomains": ["example.com", "example.org"]
              }
            }
          }
        }
      }

    Contributed by @​Jayllyz

  • noConsole now accepts an option that specifies some allowed calls on console. Contributed by @​Conaclos

  • Add an ignoreNull option for noDoubleEquals.

    By default the rule allows loose comparisons against null.
    The option ignoreNull can be set to false for reporting loose comparison against null.

    Contributed by @​peaBerberian.

  • noDuplicateObjectKeys now works for JSON and JSONC files. Contributed by @​ematipico

  • noInvalidUseBeforeDeclaration now reports direct use of an enum member before its declaration.

    In the following code, A is reported as use before its declaration.

    enum E {
      B = A << 1,
      A = 1,
    }

    Contributed by @​Conaclos

  • noNodejsModules now ignores imports of a package which has the same name as a Node.js module. Contributed by @​Conaclos

  • noNodejsModules now ignores type-only imports (#​1674).

    The rule no longer reports type-only imports such as:

    import type assert from "assert";
    import type * as assert2 from "assert";

    Contributed by @​Conaclos

  • noRedundantUseStrict no longer reports "use strict" directives when the package.json marks explicitly the file as a script using the field "type": "commonjs". Contributed by @​ematipico

  • noStaticOnlyClass no longer reports a class that extends another class (#​3612). Contributed by @​errmayank

  • noUndeclaredVariables no longer reports a direct reference to an enum member (#​2974).

    In the following code, the A reference is no longer reported as an undeclared variable.

    enum E {
      A = 1,
      B = A << 1,
    }

    Contributed by @​Conaclos

  • noUndeclaredVariables recognized Svelte 5 runes in Svelte components and svelte files.

    Svelte 5 introduced runes.
    The rule now recognizes Svelte 5 runes in files ending with the .svelte, .svelte.js or .svelte.ts extensions.

    Contributed by @​Conaclos

  • noUnusedVariables now checks TypeScript declaration files.

    This allows to report a type that is unused because it isn't exported.
    Global declarations files (declarations files without exports and imports) are still ignored.

    Contributed by @​Conaclos

  • useFilenamingConvention now supports unicase letters.

    unicase letters have a single case: they are neither uppercase nor lowercase.
    Biome now accepts filenames in unicase.
    For example, the filename 안녕하세요 is now accepted.

    We still reject a name that mixes unicase characters with lowercase or uppercase characters.
    For example, the filename A안녕하세요 is rejected.

    This change also fixes #​3353.
    Filenames consisting only of numbers are now accepted.

    Contributed by @​Conaclos

  • useFilenamingConvention now supports Next.js/Nuxt/Astro dynamic routes (#​3465).

    Next.js, SolidStart, Nuxt, and Astro support dynamic routes such as [...slug].js and [[...slug]].js.

    Biome now recognizes this syntax. slug must contain only alphanumeric characters.

    Contributed by @​Conaclos

  • useExportType no longer reports empty export (#​3535).

    An empty export {} allows you to force TypeScript to consider a file with no imports and exports as an EcmaScript module.
    While export type {} is valid, it is more common to use export {}.
    Users may find it confusing that the linter asks them to convert it to export type {}.
    Also, a bundler should be able to remove export {} as well as export type {}.
    So it is not so useful to report export {}.

    Contributed by @​Conaclos

Bug fixes

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link

changeset-bot bot commented Sep 9, 2024

⚠️ No Changeset found

Latest commit: 9c7483a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

pkg-pr-new bot commented Sep 9, 2024

Open in Stackblitz

@aria-ui/collection

pnpm add https://pkg.pr.new/ocavue/aria-ui/@aria-ui/collection@147

@aria-ui/combobox

pnpm add https://pkg.pr.new/ocavue/aria-ui/@aria-ui/combobox@147

@aria-ui/core

pnpm add https://pkg.pr.new/ocavue/aria-ui/@aria-ui/core@147

@aria-ui/listbox

pnpm add https://pkg.pr.new/ocavue/aria-ui/@aria-ui/listbox@147

@aria-ui/menu

pnpm add https://pkg.pr.new/ocavue/aria-ui/@aria-ui/menu@147

@aria-ui/overlay

pnpm add https://pkg.pr.new/ocavue/aria-ui/@aria-ui/overlay@147

@aria-ui/popover

pnpm add https://pkg.pr.new/ocavue/aria-ui/@aria-ui/popover@147

@aria-ui/tooltip

pnpm add https://pkg.pr.new/ocavue/aria-ui/@aria-ui/tooltip@147

@aria-ui/presence

pnpm add https://pkg.pr.new/ocavue/aria-ui/@aria-ui/presence@147

@aria-ui/select

pnpm add https://pkg.pr.new/ocavue/aria-ui/@aria-ui/select@147

commit: 9c7483a

@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from f14f8d7 to 402c4cd Compare September 9, 2024 11:06
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from 402c4cd to 8c66466 Compare September 9, 2024 17:02
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from 8c66466 to 6cb1c4d Compare September 9, 2024 23:06
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from 6cb1c4d to e9698b8 Compare September 10, 2024 23:15
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from e9698b8 to be70065 Compare September 12, 2024 16:17
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from be70065 to fae0974 Compare September 12, 2024 22:22
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from fae0974 to a41600d Compare September 13, 2024 13:09
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from a41600d to 08553ab Compare September 13, 2024 18:09
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from 08553ab to 8931c10 Compare September 13, 2024 21:06
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from 8931c10 to d98a6d3 Compare September 14, 2024 06:16
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from d98a6d3 to 419b3c3 Compare September 15, 2024 07:02
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from 419b3c3 to ee2f207 Compare September 15, 2024 18:55
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from ee2f207 to 7e3be05 Compare September 15, 2024 22:12
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from d411957 to 305e08b Compare October 1, 2024 09:42
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from 305e08b to 1758e92 Compare October 1, 2024 15:28
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from 1758e92 to 302bfef Compare October 1, 2024 21:58
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from 302bfef to 14654b2 Compare October 2, 2024 15:55
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from 14654b2 to a80b41d Compare October 2, 2024 18:34
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from a80b41d to d7af2cb Compare October 3, 2024 16:24
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from d7af2cb to 6aa2151 Compare October 3, 2024 19:47
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from 6aa2151 to 16f5ec1 Compare October 3, 2024 22:24
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from 16f5ec1 to 78d89ba Compare October 4, 2024 12:43
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from 78d89ba to b93488a Compare October 4, 2024 19:25
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from b93488a to 00dc7c2 Compare October 4, 2024 22:42
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from 00dc7c2 to a837f82 Compare October 5, 2024 14:36
@renovate renovate bot force-pushed the renovate/dependencies-non-major branch from a837f82 to 9c7483a Compare October 5, 2024 16:00
@ocavue ocavue merged commit b12b6c6 into master Oct 5, 2024
5 checks passed
@ocavue ocavue deleted the renovate/dependencies-non-major branch October 5, 2024 16:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant