Bump the packages group with 7 updates

[dependabot]

Bumps the packages group with 7 updates:

Package	From	To
@types/node	24.5.1	24.5.2
vercel	48.0.2	48.0.3
vite	7.1.5	7.1.6
@esbuild/openharmony-arm64	0.25.9	0.25.10
@vercel/hono	0.0.25	0.1.0
baseline-browser-mapping	2.8.5	2.8.6
electron-to-chromium	1.5.221	1.5.222

Updates @types/node from 24.5.1 to 24.5.2

Commits

• See full diff in compare view

Updates vercel from 48.0.2 to 48.0.3

Release notes

Sourced from vercel's releases.

vercel@48.0.3

Patch Changes

• fix(cli): handle triggering re-auth with legacy token + flags (#13955)

  If the CLI was using a legacy token (ie, was signed in on a version previous to 48.0.0) and did not have a SAML authorization for a team resource, commands with flags unknown to vc login failed to initiate the SAML re-authentication flow as we were parsing all arguments. This change ensures that the user is prompted to log in again in such cases.

• Updated dependencies [426aca07b47590a0f1b7631e92c8776d5f8d661d]:

  • @​vercel/hono@​0.1.0
  • @​vercel/h3@​0.1.0

Changelog

Sourced from vercel's changelog.

48.0.3

Patch Changes

• fix(cli): handle triggering re-auth with legacy token + flags (#13955)

  If the CLI was using a legacy token (ie, was signed in on a version previous to 48.0.0) and did not have a SAML authorization for a team resource, commands with flags unknown to vc login failed to initiate the SAML re-authentication flow as we were parsing all arguments. This change ensures that the user is prompted to log in again in such cases.

• Updated dependencies [426aca07b47590a0f1b7631e92c8776d5f8d661d]:

  • @​vercel/hono@​0.1.0
  • @​vercel/h3@​0.1.0

Commits

• 341094e Version Packages (#13951)
• 4184285 fix(cli): handle triggering re-auth with legacy token + flags (#13955)
• 426aca0 [frameworks][h3] Add h3 detection and builder (#13942)
• 07f0b2b Fix typescript dep (#13945)
• See full diff in compare view

Updates vite from 7.1.5 to 7.1.6

Release notes

Sourced from vite's releases.

v7.1.6

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

7.1.6 (2025-09-18)

Bug Fixes

• deps: update all non-major dependencies (#20773) (88af2ae)
• esbuild: inject esbuild helper functions with minified $ variables correctly (#20761) (7e8e004)
• fallback terser to main thread when nameCache is provided (#20750) (a679a64)
• types: strict env typings fail when skipLibCheck is false (#20755) (cc54e29)

Miscellaneous Chores

• deps: update rolldown-related dependencies (#20675) (a67bb5f)
• deps: update rolldown-related dependencies (#20772) (d785e72)

Commits

• 54377f7 release: v7.1.6
• 88af2ae fix(deps): update all non-major dependencies (#20773)
• d785e72 chore(deps): update rolldown-related dependencies (#20772)
• cc54e29 fix(types): strict env typings fail when skipLibCheck is false (#20755)
• 7e8e004 fix(esbuild): inject esbuild helper functions with minified $ variables cor...
• a679a64 fix: fallback terser to main thread when nameCache is provided (#20750)
• a67bb5f chore(deps): update rolldown-related dependencies (#20675)
• See full diff in compare view

Updates @esbuild/openharmony-arm64 from 0.25.9 to 0.25.10

Release notes

Sourced from @​esbuild/openharmony-arm64's releases.

v0.25.10

• Fix a panic in a minification edge case (#4287)

  This release fixes a panic due to a null pointer that could happen when esbuild inlines a doubly-nested identity function and the final result is empty. It was fixed by emitting the value undefined in this case, which avoids the panic. This case must be rare since it hasn't come up until now. Here is an example of code that previously triggered the panic (which only happened when minifying):

  function identity(x) { return x }
  identity({ y: identity(123) })

• Fix @supports nested inside pseudo-element (#4265)

  When transforming nested CSS to non-nested CSS, esbuild is supposed to filter out pseudo-elements such as ::placeholder for correctness. The CSS nesting specification says the following:

  The nesting selector cannot represent pseudo-elements (identical to the behavior of the ':is()' pseudo-class). We’d like to relax this restriction, but need to do so simultaneously for both ':is()' and '&', since they’re intentionally built on the same underlying mechanisms.

  However, it seems like this behavior is different for nested at-rules such as @supports, which do work with pseudo-elements. So this release modifies esbuild's behavior to now take that into account:

  /* Original code */
  ::placeholder {
    color: red;
    body & { color: green }
    @supports (color: blue) { color: blue }
  }
  /* Old output (with --supported:nesting=false) */
  ::placeholder {
  color: red;
  }
  body :is() {
  color: green;
  }
  @​supports (color: blue) {
  {
  color: blue;
  }
  }
  /* New output (with --supported:nesting=false) */
  ::placeholder {
  color: red;
  }
  body :is() {
  color: green;
  }
  @​supports (color: blue) {
  ::placeholder {
  color: blue;
  }

... (truncated)

Changelog

Sourced from @​esbuild/openharmony-arm64's changelog.

0.25.10

• Fix a panic in a minification edge case (#4287)

  This release fixes a panic due to a null pointer that could happen when esbuild inlines a doubly-nested identity function and the final result is empty. It was fixed by emitting the value undefined in this case, which avoids the panic. This case must be rare since it hasn't come up until now. Here is an example of code that previously triggered the panic (which only happened when minifying):

  function identity(x) { return x }
  identity({ y: identity(123) })

• Fix @supports nested inside pseudo-element (#4265)

  When transforming nested CSS to non-nested CSS, esbuild is supposed to filter out pseudo-elements such as ::placeholder for correctness. The CSS nesting specification says the following:

  The nesting selector cannot represent pseudo-elements (identical to the behavior of the ':is()' pseudo-class). We’d like to relax this restriction, but need to do so simultaneously for both ':is()' and '&', since they’re intentionally built on the same underlying mechanisms.

  However, it seems like this behavior is different for nested at-rules such as @supports, which do work with pseudo-elements. So this release modifies esbuild's behavior to now take that into account:

  /* Original code */
  ::placeholder {
    color: red;
    body & { color: green }
    @supports (color: blue) { color: blue }
  }
  /* Old output (with --supported:nesting=false) */
  ::placeholder {
  color: red;
  }
  body :is() {
  color: green;
  }
  @​supports (color: blue) {
  {
  color: blue;
  }
  }
  /* New output (with --supported:nesting=false) */
  ::placeholder {
  color: red;
  }
  body :is() {
  color: green;
  }
  @​supports (color: blue) {
  ::placeholder {
  color: blue;

... (truncated)

Commits

• d6b668f publish 0.25.10 to npm
• 5088c19 refactor: use strings.Builder (#4290)
• 755da31 run make update-compat-table
• a1d9c86 fix #4287: marked the wrong issue as fixed
• 73a0b2a fix #4286: minifier panic due to identity function
• 134dadf fix #4265: @supports nested inside ::pseudo
• See full diff in compare view

Updates @vercel/hono from 0.0.25 to 0.1.0

Release notes

Sourced from @​vercel/hono's releases.

@​vercel/hono@​0.1.0

Minor Changes

• Add h3 zero config support (#13942)

Changelog

Sourced from @​vercel/hono's changelog.

0.1.0

Minor Changes

• Add h3 zero config support (#13942)

Commits

• 341094e Version Packages (#13951)
• See full diff in compare view

Updates baseline-browser-mapping from 2.8.5 to 2.8.6

Commits

• ece0447 Patch to 2.8.6 because browser or feature data changed
• 0f29244 Browser or feature data changed
• 2b1770f Updating static site
• See full diff in compare view

Updates electron-to-chromium from 1.5.221 to 1.5.222

Commits

• c48d6aa 1.5.222
• 3ed4b5e generate new version
• See full diff 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
github-rest-api-executor	Error			Sep 18, 2025 10:32pm