Skip to content

build(deps): bump the npm-dependencies group across 1 directory with 22 updates - #10

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-dependencies-310df795a5
Open

build(deps): bump the npm-dependencies group across 1 directory with 22 updates#10
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-dependencies-310df795a5

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 30, 2026

Copy link
Copy Markdown
Contributor

Bumps the npm-dependencies group with 22 updates in the / directory:

Package From To
@azerothjs/cli 2.0.0-beta.2 2.1.0
@vitest/coverage-v8 5.0.0 5.0.2
@azerothjs/http 2.0.0-beta.2 2.1.0
@azerothjs/kit 2.0.0-beta.2 2.1.0
@azerothjs/schema 2.0.0-beta.2 2.1.0
azerothjs 2.0.0-beta.2 2.1.0
viem 2.56.3 2.56.9
@azerothjs/compiler 2.0.0-beta.2 2.1.0
@azerothjs/devtools 2.0.0-beta.2 2.1.0
@azerothjs/eslint-plugin 2.0.0-beta.2 2.1.0
@azerothjs/language-server 2.0.0-beta.2 2.1.0
@azerothjs/testing 2.0.0-beta.2 2.1.0
@azerothjs/typescript-plugin 2.0.0-beta.2 2.1.0
@web3icons/core 4.0.55 4.0.56
eslint 10.10.0 10.11.0
lucide-static 1.45.0 1.48.0
typescript-eslint 8.70.0 8.70.1
vite 8.3.0 8.3.1
vitest 5.0.0 5.0.2
@azerothjs/logger 2.0.0-beta.2 2.1.0
@azerothjs/ws 2.0.0-beta.2 2.1.0
@types/node 26.5.1 26.6.3

Updates @azerothjs/cli from 2.0.0-beta.2 to 2.1.0

Release notes

Sourced from @​azerothjs/cli's releases.

v2.1.0

Install

npm create azeroth@latest my-app  # scaffold a new app
npm install azerothjs@2.1.0       # add to an existing one

Every @azerothjs/* package ships at this same version - the monorepo is versioned in lockstep. Editor plugins are attached to this release: the .vsix for VS Code, the .zip for JetBrains (Settings -> Plugins -> Install Plugin from Disk).

What changed

This release is too large to reproduce in full here. Every entry, with its reasoning and migration notes, is in the changelog linked below.

  • Added
  • Changed
  • Fixed
  • Security
  • Fixed
  • Changed
  • Added
  • Fixed
  • Changed
  • Fixed

Full changelog

Full Changelog: AzerothJS/AzerothJS@v1.1.0...v2.1.0

v2.1.0-beta.2

Install

npm create azeroth@latest my-app    # scaffold a new app
npm install azerothjs@2.1.0-beta.2  # add to an existing one

Every @azerothjs/* package ships at this same version - the monorepo is versioned

... (truncated)

Changelog

Sourced from @​azerothjs/cli's changelog.

[2.1.0] - 2026-09-19

Added

  • @azerothjs/kit/dev - development runs the same page mount production does. devPages({ root, entry, pages, routes, app }) creates a vite server in middleware mode over the application half, loads the SSR entry from SOURCE, and mounts the pages with mountPages: the same call, the same route table, the same renderer. It returns a DevSession - app (the App a pipeline wraps), before (the connect middleware serve takes), attach(server) and close() - and the entry module keeps the two exports everything else already reads, routes and renderPage. The session reloads that entry, re-reads index.html and re-mounts the pages on the first request after a change; a first build that fails answers an html navigation with a readable error page naming the file, the line and the frame, and every other request with the app's own error envelope, while a LATER failure keeps the previous build serving and prints one line saying so. The process never exits for an application error.

    attach(served.server) is the part with no second socket in it. Vite is handed a relay it never listens on, so the HMR client dials the page's own origin and the app's own server forwards the upgrade: no port to bind, none to collide with, and a tab survives the server process restarting under node --watch - it reconnects and reloads itself, which an HMR port that moves per restart cannot do. A misconfiguration that vite itself reports nothing about is refused at startup naming the setting and the config file: server.proxy, a base other than /, server.watch: null, and port, clientPort or host under server.ws or its deprecated server.hmr spelling. The kit declares NOTHING about vite - no dependency, and no peer, optional or otherwise - so the copy the app itself installs is the one loaded, and a production image built with npm ci --omit=dev carries none.

  • @azerothjs/kit/dev/entry, a vite-free module exporting SSR_SOURCE_ENTRY. One name for the SSR entry as it exists in source (src/entry.server.ts), importable by anything that must not pull vite in. The CLI's plan exports the constant it had kept private and the plan suite pins the two equal, so the build step and the dev session can no longer drift apart.

  • KitOptions.shell - the document html as TEXT, in place of clientDir, for a mount with no built client on disk. Every page mounts and renders as it does in production, minus what only a build can provide: static pages render live, the asset and /assets handlers are not registered, /index.html is the app's own 404, cache is ignored, and images is a mount error naming the fix (register /_image on the server). Mount-time validation is unchanged and runs against the mode the route DECLARES, so a static page with an action and a static page under a guarded chain are the same refusals they are in production.

  • A declared dev capability, "azeroth": { "dev": "server" } in a fullstack root. With it azeroth dev plans ONE step - the server half, which now serves the client itself - instead of a server step plus a vite step; a root resolved through --app/--server overrides cannot opt in, and the plan says so. azeroth doctor gains two checks: whether the declared capability is actually backed by an @azerothjs/kit/dev import in the server entry (a warning, since a session factored into another module is legitimate), and which copy of vite the session will really load, reported with its version beside both halves' declared ranges.

  • revalidate(path), exported from @azerothjs/kit. One function, no handle and no key format: it marks a page so the next reader of any copy of it renders fresh, for a write that

... (truncated)

Commits
  • 3f5412f chore(release): v2.1.0
  • d1ba21c fix(azerothjs,compiler): a plain write to a state stores the value it was giv...
  • e727abc feat(kit,cli,create-azeroth): serve the same page contract in dev as in produ...
  • 87cc8dc fix(release): bump the editor lockfile with its manifest
  • e4f0a2d fix(http,kit,schema): harden the server stack
  • 3b817ba docs: prepare the READMEs for a documentation site
  • 4519726 chore: add the MIT copyright header to every source file
  • e8ad231 docs: rewrite the source documentation across every package
  • 7d92691 fix(compiler,devtools,tooling): diagnostics, bridge hardening, shipped guides
  • cfcead0 fix(release): wipe dist before building the five packages that did not
  • Additional commits viewable in compare view

Updates @vitest/coverage-v8 from 5.0.0 to 5.0.2

Release notes

Sourced from @​vitest/coverage-v8's releases.

v5.0.2

   🐞 Bug Fixes

    View changes on GitHub

v5.0.1

   🚀 Features

   🐞 Bug Fixes

... (truncated)

Commits

Updates @azerothjs/http from 2.0.0-beta.2 to 2.1.0

Release notes

Sourced from @​azerothjs/http's releases.

v2.1.0

Install

npm create azeroth@latest my-app  # scaffold a new app
npm install azerothjs@2.1.0       # add to an existing one

Every @azerothjs/* package ships at this same version - the monorepo is versioned in lockstep. Editor plugins are attached to this release: the .vsix for VS Code, the .zip for JetBrains (Settings -> Plugins -> Install Plugin from Disk).

What changed

This release is too large to reproduce in full here. Every entry, with its reasoning and migration notes, is in the changelog linked below.

  • Added
  • Changed
  • Fixed
  • Security
  • Fixed
  • Changed
  • Added
  • Fixed
  • Changed
  • Fixed

Full changelog

Full Changelog: AzerothJS/AzerothJS@v1.1.0...v2.1.0

v2.1.0-beta.2

Install

npm create azeroth@latest my-app    # scaffold a new app
npm install azerothjs@2.1.0-beta.2  # add to an existing one

Every @azerothjs/* package ships at this same version - the monorepo is versioned

... (truncated)

Changelog

Sourced from @​azerothjs/http's changelog.

[2.1.0] - 2026-09-19

Added

  • @azerothjs/kit/dev - development runs the same page mount production does. devPages({ root, entry, pages, routes, app }) creates a vite server in middleware mode over the application half, loads the SSR entry from SOURCE, and mounts the pages with mountPages: the same call, the same route table, the same renderer. It returns a DevSession - app (the App a pipeline wraps), before (the connect middleware serve takes), attach(server) and close() - and the entry module keeps the two exports everything else already reads, routes and renderPage. The session reloads that entry, re-reads index.html and re-mounts the pages on the first request after a change; a first build that fails answers an html navigation with a readable error page naming the file, the line and the frame, and every other request with the app's own error envelope, while a LATER failure keeps the previous build serving and prints one line saying so. The process never exits for an application error.

    attach(served.server) is the part with no second socket in it. Vite is handed a relay it never listens on, so the HMR client dials the page's own origin and the app's own server forwards the upgrade: no port to bind, none to collide with, and a tab survives the server process restarting under node --watch - it reconnects and reloads itself, which an HMR port that moves per restart cannot do. A misconfiguration that vite itself reports nothing about is refused at startup naming the setting and the config file: server.proxy, a base other than /, server.watch: null, and port, clientPort or host under server.ws or its deprecated server.hmr spelling. The kit declares NOTHING about vite - no dependency, and no peer, optional or otherwise - so the copy the app itself installs is the one loaded, and a production image built with npm ci --omit=dev carries none.

  • @azerothjs/kit/dev/entry, a vite-free module exporting SSR_SOURCE_ENTRY. One name for the SSR entry as it exists in source (src/entry.server.ts), importable by anything that must not pull vite in. The CLI's plan exports the constant it had kept private and the plan suite pins the two equal, so the build step and the dev session can no longer drift apart.

  • KitOptions.shell - the document html as TEXT, in place of clientDir, for a mount with no built client on disk. Every page mounts and renders as it does in production, minus what only a build can provide: static pages render live, the asset and /assets handlers are not registered, /index.html is the app's own 404, cache is ignored, and images is a mount error naming the fix (register /_image on the server). Mount-time validation is unchanged and runs against the mode the route DECLARES, so a static page with an action and a static page under a guarded chain are the same refusals they are in production.

  • A declared dev capability, "azeroth": { "dev": "server" } in a fullstack root. With it azeroth dev plans ONE step - the server half, which now serves the client itself - instead of a server step plus a vite step; a root resolved through --app/--server overrides cannot opt in, and the plan says so. azeroth doctor gains two checks: whether the declared capability is actually backed by an @azerothjs/kit/dev import in the server entry (a warning, since a session factored into another module is legitimate), and which copy of vite the session will really load, reported with its version beside both halves' declared ranges.

  • revalidate(path), exported from @azerothjs/kit. One function, no handle and no key format: it marks a page so the next reader of any copy of it renders fresh, for a write that

... (truncated)

Commits
  • 3f5412f chore(release): v2.1.0
  • d1ba21c fix(azerothjs,compiler): a plain write to a state stores the value it was giv...
  • 47fa21a feat(azerothjs,http,kit,create-azeroth): hand the request to every loader, gu...
  • 84b8b49 fix(http): refuse a reply at a status the route never declared, at compile ti...
  • 0753f70 fix(http,kit): one containment rule for static files, the prerendered seed an...
  • d1c0d97 fix(kit): tell shared caches the truth about a negotiated page
  • ca59c55 fix(http): keep an abandoned upload from killing the process
  • 8f6f52a fix(http): accept a same-origin form submit whose Origin the browser blanked
  • 3596095 fix(http): keep a cancelled static file download from killing the process
  • fc828b4 fix(http): keep a cancelled compressed download from killing the process
  • Additional commits viewable in compare view

Updates @azerothjs/kit from 2.0.0-beta.2 to 2.1.0

Release notes

Sourced from @​azerothjs/kit's releases.

v2.1.0

Install

npm create azeroth@latest my-app  # scaffold a new app
npm install azerothjs@2.1.0       # add to an existing one

Every @azerothjs/* package ships at this same version - the monorepo is versioned in lockstep. Editor plugins are attached to this release: the .vsix for VS Code, the .zip for JetBrains (Settings -> Plugins -> Install Plugin from Disk).

What changed

This release is too large to reproduce in full here. Every entry, with its reasoning and migration notes, is in the changelog linked below.

  • Added
  • Changed
  • Fixed
  • Security
  • Fixed
  • Changed
  • Added
  • Fixed
  • Changed
  • Fixed

Full changelog

Full Changelog: AzerothJS/AzerothJS@v1.1.0...v2.1.0

v2.1.0-beta.2

Install

npm create azeroth@latest my-app    # scaffold a new app
npm install azerothjs@2.1.0-beta.2  # add to an existing one

Every @azerothjs/* package ships at this same version - the monorepo is versioned

... (truncated)

Changelog

Sourced from @​azerothjs/kit's changelog.

[2.1.0] - 2026-09-19

Added

  • @azerothjs/kit/dev - development runs the same page mount production does. devPages({ root, entry, pages, routes, app }) creates a vite server in middleware mode over the application half, loads the SSR entry from SOURCE, and mounts the pages with mountPages: the same call, the same route table, the same renderer. It returns a DevSession - app (the App a pipeline wraps), before (the connect middleware serve takes), attach(server) and close() - and the entry module keeps the two exports everything else already reads, routes and renderPage. The session reloads that entry, re-reads index.html and re-mounts the pages on the first request after a change; a first build that fails answers an html navigation with a readable error page naming the file, the line and the frame, and every other request with the app's own error envelope, while a LATER failure keeps the previous build serving and prints one line saying so. The process never exits for an application error.

    attach(served.server) is the part with no second socket in it. Vite is handed a relay it never listens on, so the HMR client dials the page's own origin and the app's own server forwards the upgrade: no port to bind, none to collide with, and a tab survives the server process restarting under node --watch - it reconnects and reloads itself, which an HMR port that moves per restart cannot do. A misconfiguration that vite itself reports nothing about is refused at startup naming the setting and the config file: server.proxy, a base other than /, server.watch: null, and port, clientPort or host under server.ws or its deprecated server.hmr spelling. The kit declares NOTHING about vite - no dependency, and no peer, optional or otherwise - so the copy the app itself installs is the one loaded, and a production image built with npm ci --omit=dev carries none.

  • @azerothjs/kit/dev/entry, a vite-free module exporting SSR_SOURCE_ENTRY. One name for the SSR entry as it exists in source (src/entry.server.ts), importable by anything that must not pull vite in. The CLI's plan exports the constant it had kept private and the plan suite pins the two equal, so the build step and the dev session can no longer drift apart.

  • KitOptions.shell - the document html as TEXT, in place of clientDir, for a mount with no built client on disk. Every page mounts and renders as it does in production, minus what only a build can provide: static pages render live, the asset and /assets handlers are not registered, /index.html is the app's own 404, cache is ignored, and images is a mount error naming the fix (register /_image on the server). Mount-time validation is unchanged and runs against the mode the route DECLARES, so a static page with an action and a static page under a guarded chain are the same refusals they are in production.

  • A declared dev capability, "azeroth": { "dev": "server" } in a fullstack root. With it azeroth dev plans ONE step - the server half, which now serves the client itself - instead of a server step plus a vite step; a root resolved through --app/--server overrides cannot opt in, and the plan says so. azeroth doctor gains two checks: whether the declared capability is actually backed by an @azerothjs/kit/dev import in the server entry (a warning, since a session factored into another module is legitimate), and which copy of vite the session will really load, reported with its version beside both halves' declared ranges.

  • revalidate(path), exported from @azerothjs/kit. One function, no handle and no key format: it marks a page so the next reader of any copy of it renders fresh, for a write that

... (truncated)

Commits
  • 3f5412f chore(release): v2.1.0
  • d1ba21c fix(azerothjs,compiler): a plain write to a state stores the value it was giv...
  • 47fa21a feat(azerothjs,http,kit,create-azeroth): hand the request to every loader, gu...
  • 9d9e7bf fix(kit): a write marks the ISR page it lands on and revalidate() marks one f...
  • e727abc feat(kit,cli,create-azeroth): serve the same page contract in dev as in produ...
  • 4579dd8 fix(azerothjs,kit): hand the url prefix to the client the way the language is...
  • fb26997 fix(kit): regenerate an ISR page in its language, keep the copy through a fai...
  • 765ff9c fix(kit): decide the language prefix on the path the router matched, and serv...
  • 0753f70 fix(http,kit): one containment rule for static files, the prerendered seed an...
  • ffbf8f5 fix(azerothjs): judge a loader that throws synchronously as one that rejects
  • Additional commits viewable in compare view

Updates @azerothjs/schema from 2.0.0-beta.2 to 2.1.0

Release notes

Sourced from @​azerothjs/schema's releases.

v2.1.0

Install

npm create azeroth@latest my-app  # scaffold a new app
npm install azerothjs@2.1.0       # add to an existing one

Every @azerothjs/* package ships at this same version - the monorepo is versioned in lockstep. Editor plugins are attached to this release: the .vsix for VS Code, the .zip for JetBrains (Settings -> Plugins -> Install Plugin from Disk).

What changed

This release is too large to reproduce in full here. Every entry, with its reasoning and migration notes, is in the changelog linked below.

  • Added
  • Changed
  • Fixed
  • Security
  • Fixed
  • Changed
  • Added
  • Fixed
  • Changed
  • Fixed

Full changelog

Full Changelog: AzerothJS/AzerothJS@v1.1.0...v2.1.0

v2.1.0-beta.2

Install

npm create azeroth@latest my-app    # scaffold a new app
npm install azerothjs@2.1.0-beta.2  # add to an existing one

Every @azerothjs/* package ships at this same version - the monorepo is versioned

... (truncated)

Changelog

Sourced from @​azerothjs/schema's changelog.

[2.1.0] - 2026-09-19

Added

  • @azerothjs/kit/dev - development runs the same page mount production does. devPages({ root, entry, pages, routes, app }) creates a vite server in middleware mode over the application half, loads the SSR entry from SOURCE, and mounts the pages with mountPages: the same call, the same route table, the same renderer. It returns a DevSession - app (the App a pipeline wraps), before (the connect middleware serve takes), attach(server) and close() - and the entry module keeps the two exports everything else already reads, routes and renderPage. The session reloads that entry, re-reads index.html and re-mounts the pages on the first request after a change; a first build that fails answers an html navigation with a readable error page naming the file, the line and the frame, and every other request with the app's own error envelope, while a LATER failure keeps the previous build serving and prints one line saying so. The process never exits for an application error.

    attach(served.server) is the part with no second socket in it. Vite is handed a relay it never listens on, so the HMR client dials the page's own origin and the app's own server forwards the upgrade: no port to bind, none to collide with, and a tab survives the server process restarting under node --watch - it reconnects and reloads itself, which an HMR port that moves per restart cannot do. A misconfiguration that vite itself reports nothing about is refused at startup naming the setting and the config file: server.proxy, a base other than /, server.watch: null, and port, clientPort or host under server.ws or its deprecated server.hmr spelling. The kit declares NOTHING about vite - no dependency, and no peer, optional or otherwise - so the copy the app itself installs is the one loaded, and a production image built with npm ci --omit=dev carries none.

  • @azerothjs/kit/dev/entry, a vite-free module exporting SSR_SOURCE_ENTRY. One name for the SSR entry as it exists in source (src/entry.server.ts), importable by anything that must not pull vite in. The CLI's plan exports the constant it had kept private and the plan suite pins the two equal, so the build step and the dev session can no longer drift apart.

  • KitOptions.shell - the document html as TEXT, in place of clientDir, for a mount with no built client on disk. Every page mounts and renders as it does in production, minus what only a build can provide: static pages render live, the asset and /assets handlers are not registered, /index.html is the app's own 404, cache is ignored, and images is a mount error naming the fix (register /_image on the server). Mount-time validation is unchanged and runs against the mode the route DECLARES, so a static page with an action and a static page under a guarded chain are the same refusals they are in production.

  • A declared dev capability, "azeroth": { "dev": "server" } in a fullstack root. With it azeroth dev plans ONE step - the server half, which now serves the client itself - instead of a server step plus a vite step; a root resolved through --app/--server overrides cannot opt in, and the plan says so. azeroth doctor gains two checks: whether the declared capability is actually backed by an @azerothjs/kit/dev import in the server entry (a warning, since a session factored into another module is legitimate), and which copy of vite the session will really load, reported with its version beside both halves' declared ranges.

  • revalidate(path), exported from @azerothjs/kit. One function, no handle and no key format: it marks a page so the next reader of any copy of it renders fresh, for a write that

... (truncated)

Commits
  • 3f5412f chore(release): v2.1.0
  • d1ba21c fix(azerothjs,compiler): a plain write to a state stores the value it was giv...
  • 14c056e docs(schema): state object()'s null prototype in its contract, and pin it
  • de0069f fix(azerothjs,schema): give a loader the declared query its cache key names
  • e4f0a2d fix(http,kit,schema): harden the server stack
  • 3b817ba docs: prepare the READMEs for a documentation site
  • 4519726 chore: add the MIT copyright header to every source file
  • e8ad231 docs: rewrite the source documentation across every package
  • b901b7f feat(schema): date() validator
  • a80f3ea fix(release): strip dangling sourcemap references from packages
  • See full diff in compare view

Updates azerothjs from 2.0.0-beta.2 to 2.1.0

Release notes

Sourced from azerothjs's releases.

v2.1.0

Install

npm create azeroth@latest my-app  # scaffold a new app
npm install azerothjs@2.1.0       # add to an existing one

Every @azerothjs/* package ships at this same version - the monorepo is versioned in lockstep. Editor plugins are attached to this release: the .vsix for VS Code, the .zip for JetBrains (Settings -> Plugins -> Install Plugin from Disk).

What changed

This release is too large to reproduce in full here. Every entry, with its reasoning and migration notes, is in the changelog linked below.

  • Added
  • Changed
  • Fixed
  • Security
  • Fixed
  • Changed
  • Added
  • Fixed
  • Changed
  • Fixed

Full changelog

Full Changelog: AzerothJS/AzerothJS@v1.1.0...v2.1.0

v2.1.0-beta.2

Install

npm create azeroth@latest my-app    # scaffold a new app
npm install azerothjs@2.1.0-beta.2  # add to an existing one

Every @azerothjs/* package ships at this same version - the monorepo is versioned

... (truncated)

Changelog

Sourced from azerothjs's changelog.

[2.1.0] - 2026-09-19

Added

  • @azerothjs/kit/dev - development runs the same page mount production does. devPages({ root, entry, pages, routes, app }) creates a vite server in middleware mode over the application half, loads the SSR entry from SOURCE, and mounts the pages with mountPages: the same call, the same route table, the same renderer. It returns a DevSession - app (the App a pipeline wraps), before (the connect middleware serve takes), attach(server) and close() - and the entry module keeps the two exports everything else already reads, routes and renderPage. The session reloads that entry, re-reads index.html and re-mounts the pages on the first request after a change; a first build that fails answers an html navigation with a readable error page naming the file, the line and the frame, and every other request with the app's own error envelope, while a LATER failure keeps the previous build serving and prints one line saying so. The process never exits for an application error.

    attach(served.server) is the part with no second socket in it. Vite is handed a relay it never listens on, so the HMR client dials the page's own origin and the app's own server forwards the upgrade: no port to bind, none to collide with, and a tab survives the server process restarting under node --watch - it reconnects and reloads itself, which an HMR port that moves per restart cannot do. A misconfiguration that vite itself reports nothing about is refused at startup naming the setting and the config file: server.proxy, a base other than /, server.watch: null, and port, clientPort or host under server.ws or its deprecated server.hmr spelling. The kit declares NOTHING about vite - no dependency, and no peer, optional or otherwise - so the copy the app itself installs is the one loaded, and a production image built with npm ci --omit=dev carries none.

  • @azerothjs/kit/dev/entry, a vite-free module exporting SSR_SOURCE_ENTRY. One name for the SSR entry as it exists in source (src/entry.server.ts), importable by anything that must not pull vite in. The CLI's plan exports the constant it had kept private and the plan suite pins the two equal, so the build step and the dev session can no longer drift apart.

  • KitOptions.shell - the document html as TEXT, in place of clientDir, for a mount with no built client on disk. Every page mounts and renders as it does in production, minus what only a build can provide: static pages render live, the asset and /assets handlers are not registered, /index.html is the app's own 404, cache is ignored, and images is a mount error naming the fix (register /_image on the server). Mount-time validation is unchanged and runs against the mode the route DECLARES, so a static page with an action and a static page under a guarded chain are the same refusals they are in production.

  • A declared dev capability, "azeroth": { "dev": "server" } in a fullstack root. With it azeroth dev plans ONE step - the server half, which now serves the client itself - instead of a server step plus a vite step; a root resolved through --app/--server overrides cannot opt in, and the plan says so. azeroth doctor gains two checks: whether the declared capability is actually backed by an @azerothjs/kit/dev import in the server entry (a warning, since a session factored into another module is legitimate), and which copy of vite the session will really load, reported with its version beside both halves' declared ranges.

  • revalidate(path), exported from @azerothjs/kit. One function, no handle and no key format: it marks a page so the next reader of any copy of it renders fresh, for a write that

... (truncated)

Commits
  • 3f5412f chore(release): v2.1.0
  • d1ba21c fix(azerothjs,compiler): a plain write to a state stores the value it was giv...
  • 47fa21a feat(azerothjs,http,kit,create-azeroth): hand the request to every loader, gu...
  • 4579dd8 fix(azerothjs,kit): hand the url prefix to the client the way the language is...
  • 765ff9c fix(kit): decide the language prefix on the path the router matched, and serv...
  • 9dd5be9 fix(azerothjs): keep a server-seeded loader failure through hydration when th...
  • ffbf8f5 fix(azerothjs): judge a loader that throws synchronously as one that rejects
  • d1c0d97 fix(kit): tell shared caches the truth about a negotiated page
  • d3d7626 fix(azerothjs): keep a cancelled streamed render from killing the process
  • 33e8d86 fix(kit): gate a page action by the chain of the page it belongs to, whatever...
  • Additional commits viewable in compare view

Updates viem from 2.56.3 to 2.56.9

Release notes

Sourced from viem's releases.

viem@2.56.9

Patch Changes

  • #5123 2068265d2fefb41da2ca672f7b8ef0d221efdbde Thanks @​rabbitmainnet! - Added Rabbit Chain Testnet (chain ID 9280) to viem/chains.

  • #5124 4767ff7be7aed3845b617f8b16806d72469ea657 Thanks @​kyscott18! - Added the getStorageValues action for batch retrieval of contract storage slots.

  • #5108 5a201d9a5996a836023bdb676c8d7c0f43f9c8fa Thanks @​Lukecele! - Added Plasma mainnet addresses for USDC and EURC.

  • #5114 de663c98de19da2ffccdd1681fd616e6ed653b98 Thanks @​jxom! - Resynced Tempo contract ABIs and added the current committee address.

     // Abis.earnMerkleRewardDistributor contract calls
-functionName: 'fundWithAssets',
-args: [funder, assets, minEarnShares],
+functionName: 'fundAndPublishRoot',
+args: [settlementId, expectedRootVersion, funder, assets, minEarnShares, root, totalEntitlement, statementHash],
functionName: 'publishRoot',
-args: [root, totalEntitlement, statementHash],
+args: [expectedRootVersion, root, totalEntitlement, statementHash],
-const verifierAbi = Abis.zone
+const verifierAbi = Abis.core
-const selector = Selectors.zoneVerifier.verify
+const selector = Selectors.zoneVerifier.verify[

'verify(uint32,uint64,uint64,bytes32,uint64,(bytes32,bytes32),(bytes32,bytes32,uint64,uint64),bytes32,bytes,bytes)'
+]

  • #5112 c704647d93ed5eaabe3ca9e22fdd4f7e9132b641 Thanks @​spalladino! - Added optional maxUsedGas to simulateBlocks call results, preserving the per-call maxUsedGas reported by eth_simulateV1.

    maxUsedGas is the node's measurement of the gas used by a call before gas refunds are applied – it is not a guaranteed minimum sufficient gas limit for the call. It is undefined against nodes that do not report it, and is available on both successful and failed call results.

  • #5126 6feacb3a9066b47d3f083a0da0da2d8172577870 Thanks @​jxom! - viem/tempo: Added PropAMM actions.

    • viem@2.56.8

    Patch Changes

    viem@2.56.7

    Patch Changes

    ... (truncated)

    Commits

    Updates @azerothjs/compiler from 2.0.0-b...

    Description has been truncated

    @dependabot
    build(deps): bump the npm-dependencies group across 1 directory with …
    9080edb 
    …22 updates

Bumps the npm-dependencies group with 22 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@azerothjs/cli](https://github.com/AzerothJS/AzerothJS/tree/HEAD/packages/cli) | `2.0.0-beta.2` | `2.1.0` |
| [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) | `5.0.0` | `5.0.2` |
| [@azerothjs/http](https://github.com/AzerothJS/AzerothJS/tree/HEAD/packages/http) | `2.0.0-beta.2` | `2.1.0` |
| [@azerothjs/kit](https://github.com/AzerothJS/AzerothJS/tree/HEAD/packages/kit) | `2.0.0-beta.2` | `2.1.0` |
| [@azerothjs/schema](https://github.com/AzerothJS/AzerothJS/tree/HEAD/packages/schema) | `2.0.0-beta.2` | `2.1.0` |
| [azerothjs](https://github.com/AzerothJS/AzerothJS/tree/HEAD/packages/azerothjs) | `2.0.0-beta.2` | `2.1.0` |
| [viem](https://github.com/wevm/viem) | `2.56.3` | `2.56.9` |
| [@azerothjs/compiler](https://github.com/AzerothJS/AzerothJS/tree/HEAD/packages/compiler) | `2.0.0-beta.2` | `2.1.0` |
| [@azerothjs/devtools](https://github.com/AzerothJS/AzerothJS/tree/HEAD/packages/devtools) | `2.0.0-beta.2` | `2.1.0` |
| [@azerothjs/eslint-plugin](https://github.com/AzerothJS/AzerothJS/tree/HEAD/packages/eslint-plugin) | `2.0.0-beta.2` | `2.1.0` |
| [@azerothjs/language-server](https://github.com/AzerothJS/AzerothJS/tree/HEAD/packages/language-server) | `2.0.0-beta.2` | `2.1.0` |
| [@azerothjs/testing](https://github.com/AzerothJS/AzerothJS/tree/HEAD/packages/testing) | `2.0.0-beta.2` | `2.1.0` |
| [@azerothjs/typescript-plugin](https://github.com/AzerothJS/AzerothJS/tree/HEAD/packages/typescript-plugin) | `2.0.0-beta.2` | `2.1.0` |
| [@web3icons/core](https://github.com/0xa3k5/web3icons/tree/HEAD/packages/core) | `4.0.55` | `4.0.56` |
| [eslint](https://github.com/eslint/eslint) | `10.10.0` | `10.11.0` |
| [lucide-static](https://github.com/lucide-icons/lucide) | `1.45.0` | `1.48.0` |
| [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/typescript-eslint) | `8.70.0` | `8.70.1` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `8.3.0` | `8.3.1` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `5.0.0` | `5.0.2` |
| [@azerothjs/logger](https://github.com/AzerothJS/AzerothJS/tree/HEAD/packages/logger) | `2.0.0-beta.2` | `2.1.0` |
| [@azerothjs/ws](https://github.com/AzerothJS/AzerothJS/tree/HEAD/packages/ws) | `2.0.0-beta.2` | `2.1.0` |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `26.5.1` | `26.6.3` |



Updates `@azerothjs/cli` from 2.0.0-beta.2 to 2.1.0
- [Release notes](https://github.com/AzerothJS/AzerothJS/releases)
- [Changelog](https://github.com/AzerothJS/AzerothJS/blob/main/CHANGELOG.md)
- [Commits](https://github.com/AzerothJS/AzerothJS/commits/v2.1.0/packages/cli)

Updates `@vitest/coverage-v8` from 5.0.0 to 5.0.2
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.2/packages/coverage-v8)

Updates `@azerothjs/http` from 2.0.0-beta.2 to 2.1.0
- [Release notes](https://github.com/AzerothJS/AzerothJS/releases)
- [Changelog](https://github.com/AzerothJS/AzerothJS/blob/main/CHANGELOG.md)
- [Commits](https://github.com/AzerothJS/AzerothJS/commits/v2.1.0/packages/http)

Updates `@azerothjs/kit` from 2.0.0-beta.2 to 2.1.0
- [Release notes](https://github.com/AzerothJS/AzerothJS/releases)
- [Changelog](https://github.com/AzerothJS/AzerothJS/blob/main/CHANGELOG.md)
- [Commits](https://github.com/AzerothJS/AzerothJS/commits/v2.1.0/packages/kit)

Updates `@azerothjs/schema` from 2.0.0-beta.2 to 2.1.0
- [Release notes](https://github.com/AzerothJS/AzerothJS/releases)
- [Changelog](https://github.com/AzerothJS/AzerothJS/blob/main/CHANGELOG.md)
- [Commits](https://github.com/AzerothJS/AzerothJS/commits/v2.1.0/packages/schema)

Updates `azerothjs` from 2.0.0-beta.2 to 2.1.0
- [Release notes](https://github.com/AzerothJS/AzerothJS/releases)
- [Changelog](https://github.com/AzerothJS/AzerothJS/blob/main/CHANGELOG.md)
- [Commits](https://github.com/AzerothJS/AzerothJS/commits/v2.1.0/packages/azerothjs)

Updates `viem` from 2.56.3 to 2.56.9
- [Release notes](https://github.com/wevm/viem/releases)
- [Commits](https://github.com/wevm/viem/compare/viem@2.56.3...viem@2.56.9)

Updates `@azerothjs/compiler` from 2.0.0-beta.2 to 2.1.0
- [Release notes](https://github.com/AzerothJS/AzerothJS/releases)
- [Changelog](https://github.com/AzerothJS/AzerothJS/blob/main/CHANGELOG.md)
- [Commits](https://github.com/AzerothJS/AzerothJS/commits/v2.1.0/packages/compiler)

Updates `@azerothjs/devtools` from 2.0.0-beta.2 to 2.1.0
- [Release notes](https://github.com/AzerothJS/AzerothJS/releases)
- [Changelog](https://github.com/AzerothJS/AzerothJS/blob/main/CHANGELOG.md)
- [Commits](https://github.com/AzerothJS/AzerothJS/commits/v2.1.0/packages/devtools)

Updates `@azerothjs/eslint-plugin` from 2.0.0-beta.2 to 2.1.0
- [Release notes](https://github.com/AzerothJS/AzerothJS/releases)
- [Changelog](https://github.com/AzerothJS/AzerothJS/blob/main/CHANGELOG.md)
- [Commits](https://github.com/AzerothJS/AzerothJS/commits/v2.1.0/packages/eslint-plugin)

Updates `@azerothjs/language-server` from 2.0.0-beta.2 to 2.1.0
- [Release notes](https://github.com/AzerothJS/AzerothJS/releases)
- [Changelog](https://github.com/AzerothJS/AzerothJS/blob/main/CHANGELOG.md)
- [Commits](https://github.com/AzerothJS/AzerothJS/commits/v2.1.0/packages/language-server)

Updates `@azerothjs/testing` from 2.0.0-beta.2 to 2.1.0
- [Release notes](https://github.com/AzerothJS/AzerothJS/releases)
- [Changelog](https://github.com/AzerothJS/AzerothJS/blob/main/CHANGELOG.md)
- [Commits](https://github.com/AzerothJS/AzerothJS/commits/v2.1.0/packages/testing)

Updates `@azerothjs/typescript-plugin` from 2.0.0-beta.2 to 2.1.0
- [Release notes](https://github.com/AzerothJS/AzerothJS/releases)
- [Changelog](https://github.com/AzerothJS/AzerothJS/blob/main/CHANGELOG.md)
- [Commits](https://github.com/AzerothJS/AzerothJS/commits/v2.1.0/packages/typescript-plugin)

Updates `@web3icons/core` from 4.0.55 to 4.0.56
- [Release notes](https://github.com/0xa3k5/web3icons/releases)
- [Changelog](https://github.com/0xa3k5/web3icons/blob/main/packages/core/CHANGELOG.md)
- [Commits](https://github.com/0xa3k5/web3icons/commits/@web3icons/core@4.0.56/packages/core)

Updates `eslint` from 10.10.0 to 10.11.0
- [Release notes](https://github.com/eslint/eslint/releases)
- [Commits](eslint/eslint@v10.10.0...v10.11.0)

Updates `lucide-static` from 1.45.0 to 1.48.0
- [Release notes](https://github.com/lucide-icons/lucide/releases)
- [Commits](lucide-icons/lucide@1.45.0...1.48.0)

Updates `typescript-eslint` from 8.70.0 to 8.70.1
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/typescript-eslint/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.70.1/packages/typescript-eslint)

Updates `vite` from 8.3.0 to 8.3.1
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v8.3.1/packages/vite)

Updates `vitest` from 5.0.0 to 5.0.2
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.2/packages/vitest)

Updates `@azerothjs/logger` from 2.0.0-beta.2 to 2.1.0
- [Release notes](https://github.com/AzerothJS/AzerothJS/releases)
- [Changelog](https://github.com/AzerothJS/AzerothJS/blob/main/CHANGELOG.md)
- [Commits](https://github.com/AzerothJS/AzerothJS/commits/v2.1.0/packages/logger)

Updates `@azerothjs/ws` from 2.0.0-beta.2 to 2.1.0
- [Release notes](https://github.com/AzerothJS/AzerothJS/releases)
- [Changelog](https://github.com/AzerothJS/AzerothJS/blob/main/CHANGELOG.md)
- [Commits](https://github.com/AzerothJS/AzerothJS/commits/v2.1.0/packages/ws)

Updates `@types/node` from 26.5.1 to 26.6.3
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

---
updated-dependencies:
- dependency-name: "@azerothjs/cli"
  dependency-version: 2.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: "@vitest/coverage-v8"
  dependency-version: 5.0.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-dependencies
- dependency-name: "@azerothjs/http"
  dependency-version: 2.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: "@azerothjs/kit"
  dependency-version: 2.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: "@azerothjs/schema"
  dependency-version: 2.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: azerothjs
  dependency-version: 2.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: viem
  dependency-version: 2.56.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-dependencies
- dependency-name: "@azerothjs/compiler"
  dependency-version: 2.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: "@azerothjs/devtools"
  dependency-version: 2.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: "@azerothjs/eslint-plugin"
  dependency-version: 2.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: "@azerothjs/language-server"
  dependency-version: 2.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: "@azerothjs/testing"
  dependency-version: 2.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: "@azerothjs/typescript-plugin"
  dependency-version: 2.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: "@web3icons/core"
  dependency-version: 4.0.56
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-dependencies
- dependency-name: eslint
  dependency-version: 10.11.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: lucide-static
  dependency-version: 1.48.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: typescript-eslint
  dependency-version: 8.70.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-dependencies
- dependency-name: vite
  dependency-version: 8.3.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-dependencies
- dependency-name: vitest
  dependency-version: 5.0.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-dependencies
- dependency-name: "@azerothjs/logger"
  dependency-version: 2.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: "@azerothjs/ws"
  dependency-version: 2.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: "@types/node"
  dependency-version: 26.6.3
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
    @dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 30, 2026
    @coderabbitai

    coderabbitai Bot commented Sep 30, 2026

    Copy link
    Copy Markdown

    Important

    Review skipped

    Bot user detected.

    To trigger a single review, invoke the @coderabbitai review command.

    ⚙️ Run configuration

    Configuration used: Repository: NuraChain/Swap/.coderabbit.yaml

    Review profile: ASSERTIVE

    Plan: Advanced

    Run ID: 15647c5f-6132-4896-b8e0-06728df8c2cc

    You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

    Use the checkbox below for a quick retry:

    • 🔍 Trigger review

    Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

    ❤️ Share

    Comment @coderabbitai help to get the list of available commands.

    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

    dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

    Projects

    None yet

    Milestone

    No milestone

    Development

    Successfully merging this pull request may close these issues.

    0 participants