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

renovate · 2024-09-09T10:50:13Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@biomejs/biome (source)	`1.8.3` -> `1.9.1`
@changesets/cli (source)	`2.27.7` -> `2.27.8`
@floating-ui/dom (source)	`^1.6.10` -> `^1.6.11`
@ocavue/eslint-config	`^2.6.0` -> `^2.8.1`
@types/bun (source)	`^1.1.8` -> `^1.1.9`
@vitest/browser (source)	`^2.0.5` -> `^2.1.1`
@zag-js/dismissable	`^0.65.1` -> `^0.68.1`
@zag-js/dom-query	`^0.65.1` -> `^0.68.1`
astro (source)	`^4.15.1` -> `^4.15.7`
astrobook	`^0.4.2` -> `^0.4.4`
eslint (source)	`^9.9.1` -> `^9.10.0`
playwright (source)	`^1.46.1` -> `^1.47.1`
pnpm (source)	`9.9.0` -> `9.10.0`
tsup (source)	`^8.2.4` -> `^8.3.0`
turbo (source)	`2.1.1` -> `2.1.2`
typescript (source)	`^5.5.4` -> `^5.6.2`
vitest (source)	`^2.0.5` -> `^2.1.1`

Release Notes

biomejs/biome (@biomejs/biome)

`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

Add nursery/noProcessEnv. Contributed by @unvalley

Bug fixes

useSemanticElements now ignores alert and alertdialog roles (3858). Contributed by @Conaclos
noUndeclaredDependencies now ignores @/ imports and recognizes type imports from Definitely Typed and bun imports. Contributed by @Conaclos

Parser

`v1.9.0`

Compare Source

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

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

correctness/noInvalidNewBuiltin is deprecated. Use correctness/noInvalidBuiltinInstantiation instead.
style/useSingleCaseStatement is deprecated. Use correctness/noSwitchDeclarations instead.
suspicious/noConsoleLog is deprecated. Use suspicious/noConsole instead.

New features

Implement css suppression action. Contributed by @togami2864
Add support for GraphQL linting. Contributed by @ematipico
Add nursery/noCommonJs. Contributed by @minht11
Add nursery/noDuplicateCustomProperties. Contributed by @chansuke
Add nursery/noEnum. Contributed by @nickfla1
Add nursery/noDynamicNamespaceImportAccess. Contributed by @minht11
Add nursery/noIrregularWhitespace. Contributed by @michellocana
Add nursery/noRestrictedTypes. Contributed by @minht11
Add nursery/noSecrets. Contributed by @SaadBazaz
Add nursery/noUselessEscapeInRegex. Contributed by @Conaclos
Add nursery/noValueAtRule. Contributed by @rishabh3112
Add nursery/useAriaPropsSupportedByRole. Contributed by @ryo-ebata
Add nursery/useConsistentMemberAccessibility. Contributed by @seitarof
Add nursery/useStrictMode. Contributed by @ematipico
Add nursery/useTrimStartEnd. Contributed by @chansuke
Add nursery/noIrreguluarWhitespace. Contributed by @DerTimonius

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

noControlCharactersInRegex now corretcly handle \u escapes in unicode-aware regexes.

Previously, the rule didn't consider regex with the v flags as unicode-aware regexes.
Moreover, \uhhhh was not handled in unicode-aware regexes.

Contributed by @Conaclos
noControlCharactersInRegex now reports control characters and escape sequence of control characters in string regexes. Contributed by @Conaclos
noExcessiveNestedTestSuites: fix an edge case where the rule would alert on heavily nested zod schemas. Contributed by @dyc3
noExtraNonNullAssertion no longer reports a single non-null assertion enclosed in parentheses (#3352). Contributed by @Conaclos
noMultipleSpacesInRegularExpressionLiterals now correctly provides a code fix when Unicode characters are used. Contributed by @Conaclos
noRedeclare no longer report redeclartions for lexically scoped function declarations #3664.

In JavaScript strict mode, function declarations are lexically scoped:
they cannot be accessed outside the block where they are declared.

In non-strict mode, function declarations are hoisted to the top of the enclosing function or global scope.

Previously Biome always hoisted function declarations.
It now takes into account whether the code is in strict or non strict mode.

Contributed by @Conaclos
noUndeclaredDependencies now ignores self package imports.

Given teh following package.json:
```
{
  "name": "my-package",
  "main": "index.js"
}
```
The following import is no longer reported by the rule:
```
import * as mod from "my-package";
```
Contributed by @Conaclos
Fix [#3149] crashes that occurred when applying the noUselessFragments unsafe fixes in certain scenarios. Contributed by @unvalley
noRedeclare no longer reports a variable named as the function expression where it is declared. Contributed by @Conaclos
useAdjacentOverloadSignatures no longer reports a #private class member and a public class member that share the same name (#3309).

The following code is no longer reported:
```
class C {
  #f() {}
  g() {}
  f() {}
}
```
Contributed by @Conaclos
useAltText n olonger requests alt text for elements hidden from assistive technologies (#3316). Contributed by @robintown
useNamingConvention now accepts applying custom convention on abstract classes. Contributed by @Conaclos
useNamingConvention no longer suggests an empty fix when a name doesn't match strict Pascal case (#3561).

Previously the following code led useNamingConvention to suggest an empty fix.
The rule no longer provides a fix for this case.
```
type AAb = any
```
Contributed by @Conaclos
useNamingConvention no longer provides fixes for global TypeScript declaration files.

Global TypeScript declaration files have no epxorts and no imports.
All the declared types are available in all files of the project.
Thus, it is not safe to propose renaming only in the declaration file.

Contributed by @Conaclos
useSortedClasses lint error with Template literals (#3394). Contributed by @hangaoke1
useValidAriaValues now correctly check property types (3748).

Properties that expect a string now accept arbitrary text.
An identifiers can now be made up of any characters except ASCII whitespace.
An identifier list can now be separated by any ASCII whitespace.

Contributed by @Conaclos

Parser

Enhancements

The JSON parser now allows comments in turbo.json and jest.config.json. Contributed by @Netail and @Conaclos
The JSON parser now allows comments in files with the .json extension under the .vscode and .zed directories.

Biome recognizes are well known JSON files that allows comments and/or trailing commas.
Previously, Biome did not recognize JSON files under the .vscode and the .zed directories as JSON files that allow comments.
You had to configure Biome to recognize them:
```
{
  "overrides": [
    {
      "include": ["**/.vscode/*.json", "**/.zed/*.json"],
      "json": { "parser": { "allowComments": true } }
    }
  ]
}
```
This override is no longer needed!
Note that JSON files under the .vscode and the .zed directories don't accept trailing commas.

Contributed by @Conaclos

Bug fixes

The CSS parser now accepts emoji in identifiers (3627).

The following code is now correctly parsed:
```
p {
  --🥔-color: red;
  color: var(--🥔-color);
}
```
Contributed by @Conaclos
Fix #3287 nested selectors with pseudo-classes. Contributed by @denbezrukov
Fix #3349 allow CSS multiple ampersand support. Contributed by @denbezrukov
```
.class {
  && {
    color: red;
  }
}
```
Fix #3410 by correctly parsing break statements containing keywords.
```
out: while (true) {
  break out;
}
```
Contributed by @ah-yu
Fix #3464 by enabling JSX in .vue files that use the lang='jsx' or lang='tsx' attribute. Contributed by @ematipico

changesets/changesets (@changesets/cli)

`v2.27.8`

Compare Source

floating-ui/floating-ui (@floating-ui/dom)

`v1.6.11`

Compare Source

Patch Changes

fix: handle html relative offset
Update dependencies: @floating-ui/utils@0.2.8

ocavue/eslint-config (@ocavue/eslint-config)

`v2.8.1`

Compare Source

Bug Fixes

disable @typescript-eslint/no-unnecessary-type-assertion for markdown (#128) (2475b9d)

`v2.8.0`

Compare Source

Features

enable @typescript-eslint/no-unnecessary-type-assertion (eea1c40)

`v2.7.0`

Compare Source

Features

remove @types/eslint from dependencies (#123) (a11bff8)

vitest-dev/vitest (@vitest/browser)

`v2.1.1`

Compare Source

🐞 Bug Fixes

browser:
- Make example test callbacks async - by @aqandrew in https://github.com/vitest-dev/vitest/issues/6484 (16aa7)
- Optimize vitest-browser-vue correctly - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6490 (5cbb0)
workspace:
- Resolve glob pattern once to avoid name collision - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6489 (36b5a)

View changes on GitHub

`v2.1.0`

Compare Source

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)

  await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()

  const [firstPost] = screen.getByRole('listitem').all()

  await firstPost.getByRole('button', { name: 'Delete' }).click()

  expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

Potential Breaking Change

workspace:
- Correctly resolve workspace globs and file paths - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6316 (afdcb)
- This changes how the custom glob pattern in the workspace config is treated. Any file matching the glob is considered a Vitest config file. Any folder matching the glob pattern is treated as a workspace project and is subject to the regular config resolution (single vitest.config.ts or vite.config.ts inside the folder)
- For example, projects/* will match anything inside the projects folder. If it's a folder, we try to find the config inside that folder (if there is none, it is still treated as a project with the default config). If it's a file, it will be treated as a Vitest config. projects/**/* previously would assume that you only wanted to have folders as projects, but now it will match every single file insideprojects.
- This change doesn't affect non-glob usage.

🚀 Features

api:
- Make spec into a class instead of a tuple - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6355 (874a1)
browser:
- Move page.config to server.config, add more docs - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6252 (af2b8)
- Make iframe scalable, improve documentation - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6257 (74ca1)
- Introduce built-in locators - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6084 (3347f)
- Support v8 coverage - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6273 (34199)
- Support userEvent.upload in playwright provider - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6442 (cf148)
- Support --inspect - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6433 (0499a)
- Support --inspect-brk - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6434 (7ab0f)
cli:
- Extend existing list command to output only a list of file names - by @Ma-hawaj and @sheremet-va in [https://github

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.

changeset-bot · 2024-09-09T10:50:16Z

⚠️ No Changeset found

Latest commit: 370a1e3

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

pkg-pr-new · 2024-09-09T11:00:57Z

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/menu

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

@aria-ui/listbox

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

@aria-ui/presence

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

@aria-ui/popover

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

@aria-ui/overlay

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

@aria-ui/select

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

@aria-ui/tooltip

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

commit: 370a1e3

github-actions bot deployed to aria-ui (Preview) September 9, 2024 10:50 View deployment

renovate bot force-pushed the renovate/dependencies-non-major branch from 9887c0f to f14f8d7 Compare September 9, 2024 10:59

github-actions bot deployed to aria-ui (Preview) September 9, 2024 11:00 View deployment

renovate bot force-pushed the renovate/dependencies-non-major branch from f14f8d7 to 402c4cd Compare September 9, 2024 11:06

github-actions bot deployed to aria-ui (Preview) September 9, 2024 11:06 View deployment

renovate bot force-pushed the renovate/dependencies-non-major branch from 402c4cd to 8c66466 Compare September 9, 2024 17:02

github-actions bot deployed to aria-ui (Preview) September 9, 2024 17:03 View deployment

renovate bot force-pushed the renovate/dependencies-non-major branch from 8c66466 to 6cb1c4d Compare September 9, 2024 23:06

github-actions bot deployed to aria-ui (Preview) September 9, 2024 23:07 View deployment

renovate bot force-pushed the renovate/dependencies-non-major branch from 6cb1c4d to e9698b8 Compare September 10, 2024 23:15

github-actions bot deployed to aria-ui (Preview) September 10, 2024 23:16 View deployment

renovate bot force-pushed the renovate/dependencies-non-major branch from e9698b8 to be70065 Compare September 12, 2024 16:17

github-actions bot deployed to aria-ui (Preview) September 12, 2024 16:18 View deployment

renovate bot force-pushed the renovate/dependencies-non-major branch from be70065 to fae0974 Compare September 12, 2024 22:22

github-actions bot deployed to aria-ui (Preview) September 12, 2024 22:23 View deployment

renovate bot force-pushed the renovate/dependencies-non-major branch from fae0974 to a41600d Compare September 13, 2024 13:09

github-actions bot deployed to aria-ui (Preview) September 13, 2024 13:09 View deployment

renovate bot force-pushed the renovate/dependencies-non-major branch from a41600d to 08553ab Compare September 13, 2024 18:09

github-actions bot deployed to aria-ui (Preview) September 13, 2024 18:10 View deployment

renovate bot force-pushed the renovate/dependencies-non-major branch from 08553ab to 8931c10 Compare September 13, 2024 21:06

github-actions bot deployed to aria-ui (Preview) September 13, 2024 21:07 View deployment

renovate bot force-pushed the renovate/dependencies-non-major branch from 8931c10 to d98a6d3 Compare September 14, 2024 06:16

github-actions bot deployed to aria-ui (Preview) September 14, 2024 06:17 View deployment

renovate bot force-pushed the renovate/dependencies-non-major branch from d98a6d3 to 419b3c3 Compare September 15, 2024 07:02

github-actions bot deployed to aria-ui (Preview) September 15, 2024 07:03 View deployment

renovate bot force-pushed the renovate/dependencies-non-major branch from 419b3c3 to ee2f207 Compare September 15, 2024 18:55

github-actions bot deployed to aria-ui (Preview) September 15, 2024 18:56 View deployment

renovate bot force-pushed the renovate/dependencies-non-major branch from ee2f207 to 7e3be05 Compare September 15, 2024 22:12

github-actions bot deployed to aria-ui (Preview) September 15, 2024 22:13 View deployment

renovate bot force-pushed the renovate/dependencies-non-major branch from 7e3be05 to 6bdc91e Compare September 17, 2024 06:28

github-actions bot deployed to aria-ui (Preview) September 17, 2024 06:28 View deployment

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

370a1e3

renovate bot force-pushed the renovate/dependencies-non-major branch from 6bdc91e to 370a1e3 Compare September 18, 2024 00:43

github-actions bot deployed to aria-ui (Preview) September 18, 2024 00:44 View deployment

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

renovate bot commented Sep 9, 2024 •

edited

Loading

changeset-bot bot commented Sep 9, 2024 •

edited

Loading

pkg-pr-new bot commented Sep 9, 2024 •

edited

Loading

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

Are you sure you want to change the base?

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

Conversation

renovate bot commented Sep 9, 2024 • edited Loading

Release Notes

Analyzer

CLI

Bug fixes

Configuration

Editors

Formatter

JavaScript APIs

Linter

New Features

Bug fixes

Parser

Analyzer

CLI

New features

Enhancements

Bug fixes

Configuration

Editors

Formatter

Linter

Promoted rules

Deprecated rules

New features

Enhancements

Bug fixes

Parser

Enhancements

Bug fixes

Patch Changes

Bug Fixes

Features

Features

🐞 Bug Fixes

Potential Breaking Change

🚀 Features

Configuration

changeset-bot bot commented Sep 9, 2024 • edited Loading

⚠️ No Changeset found

pkg-pr-new bot commented Sep 9, 2024 • edited Loading

renovate bot commented Sep 9, 2024 •

edited

Loading

changeset-bot bot commented Sep 9, 2024 •

edited

Loading

pkg-pr-new bot commented Sep 9, 2024 •

edited

Loading