chore(deps): update all non-major dependencies

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence	Type	Update	Pending
@ai-sdk/vue (source)	^4.0.28 → ^4.0.31			dependencies	patch
@nuxt/ui (source)	^4.9.0 → ^4.10.0			dependencies	patch
@sveltejs/kit (source)	^2.69.3 → ^2.70.1			devDependencies	minor
ai (source)	^7.0.28 → ^7.0.31			devDependencies	patch
ai (source)	^7.0.28 → ^7.0.31			dependencies	patch
eve (source)	>=0.24.3 → >=0.25.2			peerDependencies	minor
eve (source)	^0.24.3 → ^0.25.2			devDependencies	minor
eve>ai (source)	^7.0.28 → ^7.0.31			pnpm-workspace.overrides	patch
happy-dom	^20.10.6 → ^20.11.0			devDependencies	minor
hono (source)	>=4.12.30 → >=4.12.31			peerDependencies	patch
node	22 → 22.23.1			uses-with	minor
pnpm (source)	11.11.0 → 11.15.0			packageManager	minor	11.15.1
tailwindcss (source)	^4.3.2 → ^4.3.3			dependencies	patch
tsdown (source)	^0.22.8 → ^0.22.9			devDependencies	patch	0.22.12 (+2)
vite (source)	^8.1.4 → ^8.1.5			devDependencies	patch

---

Release Notes

vercel/ai (@​ai-sdk/vue)

v4.0.31

Compare Source

Patch Changes

• Updated dependencies [70f18c3]
• Updated dependencies [cd06458]
  • ai@​7.0.31
  • @​ai-sdk/provider-utils@​5.0.11

v4.0.30

Compare Source

Patch Changes

• ai@​7.0.30

sveltejs/kit (@​sveltejs/kit)

v2.70.1

Compare Source

Patch Changes

• docs: update links to hooks documentation (#​16417)

v2.70.0

Compare Source

Minor Changes

• feat: move defineEnvVars to @sveltejs/kit/env (#​16378)

Patch Changes

• fix: enable CSRF protection in builds with a non-production NODE_ENV value (#​16313)

vercel/ai (ai)

v7.0.31

Compare Source

Patch Changes

• 70f18c3: fix(ai): emit denied tool output state for client-rejected approvals
• cd06458: fix(ai): call onInputStart before onInputAvailable during non-streaming tool calls
• Updated dependencies [cd06458]
  • @​ai-sdk/provider-utils@​5.0.11
  • @​ai-sdk/gateway@​4.0.23

v7.0.30

Compare Source

Patch Changes

• Updated dependencies [341616a]
• Updated dependencies [70fc45c]
  • @​ai-sdk/gateway@​4.0.22

vercel/eve (eve)

v0.25.2

Compare Source

Patch Changes

• a4c48a9: The integrations catalog gains 4 Chat SDK adapter channels for surfaces without a first-class eve channel (Google Chat, WhatsApp, X, and Messenger), each with a chatSdkChannel quick start. The eve channels add picker is unchanged.
• d9c49fc: Tool schemas that cannot be rehydrated into local validators no longer fail the turn. Serialized JSON Schemas first retry rehydration as JSON Schema 2020-12 (so MCP $defs references validate correctly), and schemas outside the supported conversion subset (such as inline JSON Pointer $refs) are now advertised to the model unchanged with validation left to the tool's own executor — OpenAPI operations with such schemas are kept instead of omitted.

v0.25.1

Compare Source

Patch Changes

• b2bc6b6: Make default-exported hooks emit portable extension declarations while preserving typed event handlers and authored event keys.

v0.25.0

Compare Source

Minor Changes

• b9bb8b2: Scaffold extensions with separate source and dist roots, a required wildcard eve peer, and dist-only publication. eve extension build now emits an agent-shaped JavaScript distribution with declarations, assets, and capability compatibility metadata instead of requiring author TypeScript in the published package.

Patch Changes

• 29ecffc: Build mounted source-backed workspace extensions before eve dev compiles the agent, then rebuild only the affected extension when its source changes. Failed extension builds keep the previous dist and active development generation serving.
• 46b78b8: Stop development microsandboxes on eve dev shutdown by discovering resources from their run labels and loading the application's installed microsandbox version during cleanup.
• 6a5a36a: Deliver stale HITL responses — answers to a question or approval that is no longer pending — as a new user message, letting the model decide whether the old selection still matters. A stale approval never authorizes the earlier tool call.
• f7c69b1: The Vercel Framework Preset is now reconciled with the host framework on disk when running /deploy via the TUI.
• bbec675: Extensions installed with a registry-style store layout (e.g. from npm with pnpm) now work in eve dev and eve eval. Extension modules reached through a node_modules symlink resolve their dependencies from the package's real location — matching standard resolver semantics — instead of failing with UNRESOLVED_IMPORT/ERR_MODULE_NOT_FOUND or silently picking up another copy of the dependency from the consuming app.
• 14501dc: Every eve-owned tool input is now validated against its schema before execution, so invalid calls are returned to the model for retry instead of failing the run. Subagent calls treat an empty outputSchema as absent, and OpenAPI operations with invalid schemas are omitted with a warning.

v0.24.6

Compare Source

Patch Changes

• 3029647: Update the generated Web Chat template for Next.js 16.3 preview type declarations.
• b97f1d1: Custom channel routes can now cancel a session's in-flight turn: route handlers receive a cancel({ continuationToken, turnId? }) helper addressed by the channel-local continuation token, and Session handles returned by send() and getSession() expose cancel({ turnId? }) for session-id-addressed cancellation. ClientSession.cancel() accepts the same optional turnId stale-request guard.

v0.24.5

Compare Source

Patch Changes

• bfbbe92: Add eve build --profile <path> for a machine-readable build-timing and final-output-size report. Profile collection is best-effort, so reporting failures do not fail an otherwise successful build.
• dab9889: Allow agents to remove the root-only built-in agent delegation tool with disableTool() from agent/tools/agent.ts.
• e1cb505: Retry transient network failures while reopening client session streams so active turns remain attached.
• 2568387: Cancel active local, nested, and remote subagent turns when their parent turn is cancelled. Client and eval sessions can now cancel active turns directly, and eval live-turn handles can wait for typed mid-turn events before cancellation or settlement.
• 20cd9a1: Added POST /eve/v1/session/:sessionId/cancel to the eve HTTP channel for requesting cancellation of an in-flight turn. The optional { turnId } body limits the request to the turn the caller observed; the response reports "accepted" when a cancellation hook accepts it or the benign "no_active_turn" when no resumable target exists.
• 02698fd: Fix Vercel deploys for the Next.js web channel. eve no longer scaffolds a
  vercel.json experimentalServices block, which the Vercel platform now
  rejects (it requires the services key and a stricter schema). For Next.js the
  block was also redundant — withEve() generates the eve service and
  /eve/v1/* routes into the Build Output at build time — so the scaffold now
  writes a minimal vercel.json.
• e45a066: eve link now lets you create a Vercel project or link an existing one, matching the project setup available through /model usage.
• 5f8818b: eve channels add web now updates the Vercel Framework Preset when adding a
  Next.js web channel to an already-linked eve project to prevent deployment
  failures.
• 887908c: Bundle authored modules in each development generation as one shared graph, avoiding repeated parsing and emission of dependencies for every tool.
• 376a82f: Report the root-only agent action alongside other framework tools in agent info, including whether it is active, disabled, or replaced.
• 4f2863d: Update the bundled Workflow runtime dependencies to their latest 5.0 beta releases.
• d9d3226: Fix withEve producing a broken Vercel build command in npm workspaces, where the eve module is located in the workspace root.

v0.24.4

Compare Source

Patch Changes

• d5db876: Session teardown now disposes authorization hooks without waiting on pending durable iterator reads, preventing cancelled sessions from hanging during cleanup.
• 0dbea62: Store local Workflow World data under .eve/.workflow-data for both eve dev and eve start.
• 9058962: Keep an active eve dev REPL session across successful authored-source reloads, so its next turn continues the durable conversation on the latest generation.
• 4531a3d: Route all of eve's single-file bundles through a shared Rolldown helper that always disables code splitting. This closes a remaining gap where a dynamic import reachable from a final workflow bundle could still fail with "Expected one bundled ..." during builds.
• b6e5923: Include the current continuation token in session.waiting events, and allow negative stream start indexes such as -1 to read relative to the current tail.
• 159d674: Turns are now cancellable: resuming a session's durable cancel hook ({sessionId}:cancel, with an optional turnId guard) aborts in-flight work and settles the turn as a new turn.cancelled stream event followed by session.waiting — never as a failure. Channels and stream-event hooks can handle turn.cancelled, and eve/client finalizes partially streamed messages. The HTTP cancellation API ships in a following release.

capricorn86/happy-dom (happy-dom)

v20.11.0

Compare Source

🎨 Features

• Adds support for CookieStore API - By @​TrevorBurnham in task #​1864
• Adds support for Element.checkVisibility() - By @​capricorn86 in task #​1506

honojs/hono (hono)

v4.12.31

Compare Source

actions/node-versions (node)

v22.23.1: 22.23.1

Compare Source

Node.js 22.23.1

v22.23.0: 22.23.0

Compare Source

Node.js 22.23.0

v22.22.3: 22.22.3

Compare Source

Node.js 22.22.3

v22.22.2: 22.22.2

Compare Source

Node.js 22.22.2

v22.22.1: 22.22.1

Compare Source

Node.js 22.22.1

v22.22.0: 22.22.0

Compare Source

Node.js 22.22.0

v22.21.1: 22.21.1

Compare Source

Node.js 22.21.1

v22.21.0: 22.21.0

Compare Source

Node.js 22.21.0

v22.20.0: 22.20.0

Compare Source

Node.js 22.20.0

v22.19.0: 22.19.0

Compare Source

Node.js 22.19.0

v22.18.0: 22.18.0

Compare Source

Node.js 22.18.0

v22.17.1: 22.17.1

Compare Source

Node.js 22.17.1

v22.17.0: 22.17.0

Compare Source

Node.js 22.17.0

v22.16.0: 22.16.0

Compare Source

Node.js 22.16.0

v22.15.1: 22.15.1

Compare Source

Node.js 22.15.1

v22.15.0: 22.15.0

Compare Source

Node.js 22.15.0

v22.14.0: 22.14.0

Compare Source

Node.js 22.14.0

v22.13.1: 22.13.1

Compare Source

Node.js 22.13.1

v22.13.0: 22.13.0

Compare Source

Node.js 22.13.0

v22.12.0: 22.12.0

Compare Source

Node.js 22.12.0

v22.11.0: 22.11.0

Compare Source

Node.js 22.11.0

v22.10.0: 22.10.0

Compare Source

Node.js 22.10.0

v22.9.0: 22.9.0

Compare Source

Node.js 22.9.0

v22.8.0: 22.8.0

Compare Source

Node.js 22.8.0

v22.7.0: 22.7.0

Compare Source

Node.js 22.7.0

v22.6.0: 22.6.0

Compare Source

Node.js 22.6.0

v22.5.1: 22.5.1

Compare Source

Node.js 22.5.1

v22.5.0: 22.5.0

Compare Source

Node.js 22.5.0

v22.4.1: 22.4.1

Compare Source

Node.js 22.4.1

v22.4.0: 22.4.0

Compare Source

Node.js 22.4.0

v22.3.0: 22.3.0

Compare Source

Node.js 22.3.0

v22.2.0: 22.2.0

Compare Source

Node.js 22.2.0

v22.1.0: 22.1.0

Compare Source

Node.js 22.1.0

pnpm/pnpm (pnpm)

v11.15.0: pnpm 11.15

Compare Source

Minor Changes

• Optional peer dependencies declared only via peerDependenciesMeta (for example debug's supports-color peer) are now resolved from a satisfying version already present in the dependency graph, the same way explicitly declared optional peer dependencies are. Previously such peers were only resolved this way when the package's metadata was read back from the lockfile, so an unrelated dependency change could rewrite peer resolutions across the whole lockfile.

Patch Changes

• Updated adm-zip to prevent crafted ZIP archives from causing excessive memory allocation.

• pnpm version -r no longer writes a versioning-ledger entry with no consumed intents as a bare intents: key, which the next run failed to read with ERR_PNPM_INVALID_VERSIONING_LEDGER. Empty intent lists are now written as intents: [], and the ledger reader accepts the bare form left by earlier releases.

• Fixed pnpr workspace resolution to preserve project names and versions for workspace: dependencies.

Platinum Sponsors

Gold Sponsors

v11.14.0: pnpm 11.14

Compare Source

Minor Changes

• peerDependencies now accept dependency specifiers that carry a scheme — a named-registry spec (<registry>:<version>), an npm: alias, or a file:/git/URL spec — instead of rejecting them with ERR_PNPM_INVALID_PEER_DEPENDENCY_SPECIFICATION #​13095. Such a peer is matched against the semver range carried by the specifier (work:5.x.x is checked as 5.x.x, npm:bar@^5 as ^5), or against * when it carries no version, while the original specifier still selects the package to auto-install. Bare name@version values, which are almost always a mistake, are still rejected.

• Added pnpm doctor, which diagnoses the pnpm installation and the environment it runs in: the versions and install method, whether the global bin directory is on PATH, whether the store and cache are writable, which link strategies (reflink, hardlink, symlink) the store's filesystem supports, registry connectivity, and an offline file: install that exercises the resolve/store/link path end to end. Each check reports how to fix what it finds, and the command exits non-zero when any check fails.

  Use --offline to skip the checks that need network access, --json for machine-readable output, and --benchmark to time the filesystem and install checks.

• Added support for executing multiple scripts matching a RegExp passed to pnpm run (e.g., pnpm run "/^build:.*/"), running matched scripts in deterministic lexicographical order. Restored the --sequential (-s) CLI option for pnpm run, which forces workspaceConcurrency to 1 so that matched scripts run sequentially one by one across and within packages.

Patch Changes

• Fixed pnpm install failing with ERR_PNPM_LOCKFILE_IS_SYMLINK when pnpm-lock.yaml is a symlink, as build sandboxes such as Bazel and Nix stage it #​13073. Reading a lockfile through a symlink is allowed again, and an install that leaves the lockfile unchanged no longer rewrites it, so --frozen-lockfile no longer needs to write at all. Writing a changed lockfile through a symlink is still refused, as that would redirect the write onto the symlink's target.

• Fixed frozen installs incorrectly treating equivalent Git dependency specifiers as a stale lockfile. See #​13039.

• pnpm owner ls now reports authentication and authorization failures (401/403) as dedicated errors that include the registry's response body, matching pnpm owner add/rm, instead of a generic Failed to fetch owners message.

• Recover from a metadata cache entry that disappears (concurrent cache cleanup, antivirus) after the registry has already answered the conditional request with 304 Not Modified. The metadata is re-requested once without cache validators instead of failing the install with ERR_PNPM_CACHE_MISSING_AFTER_304.

• A project pinned to a broken pnpm release via packageManager or devEngines.packageManager now reports which release is broken and what to do about it, instead of failing inside the installer. pnpm self-update already refused these releases; the version switch does too.

• Prevent broken-lockfile errors from including snippets of the lockfile's contents.

• pnpm self-update now checks that the version it installed can run before making it the active pnpm. A release that installs but cannot execute is discarded with an error instead of replacing a working installation.

• Fixed an out-of-memory regression when workspace projects concurrently resolve a package with large registry metadata pnpm/pnpm#13077.

• Fixed pnpm update rewriting exact version pins that use the = operator (for example =3.5.1) to a caret range (^3.5.1). Exact pins are now preserved and written back as the bare version. See #​12745.

Platinum Sponsors

Gold Sponsors

v11.13.1: pnpm 11.13.1

Compare Source

Patch Changes

• Fixed pnpm pack applying workspace-root ignore rules when a workspace package has its own .npmignore file.
• Keep the interactive minimumReleaseAge approval prompt visible during pnpm install. The progress reporter now pauses its redraws while a prompt is waiting for input instead of overwriting it, so the install no longer hangs on a question the user cannot see #​13019.
• Fixed pnpm self-update failing to link native platform binaries stored in sibling global virtual store slots.

v11.13.0: pnpm 11.13

Compare Source

Minor Changes

• Added versioning.epics to pnpm-workspace.yaml. An epic ties a group of member packages to a lead package, constraining every member's major version to a band derived from the lead's major: while the lead is on major M, members live in M*100 … M*100+99. Members move independently inside the band (patch, minor, and a major intent that stays in-band); a bump that would carry a member past the band ceiling is rejected until the lead advances its own major. When a release plan takes the lead to a new stable major, every member re-bases to the band floor in the same plan. Membership is matched with pnpm's package selectors — name globs, ./-prefixed directory globs, and !-prefixed negations.

• Added the team command for managing organization teams and team memberships on the registry, with create, destroy, add, rm, and ls subcommands and support for --otp, --parseable, and --json flags.

• Added native workspace release management #​12952: the new pnpm change command records change intents as changesets-compatible .changeset/*.md files (pnpm change status shows the pending release plan), and the bare pnpm version -r consumes them — bumping versions across the workspace with dependent propagation through workspace: ranges, fixed groups, a maxBump cap, --filter narrowing, and --dry-run — writing changelogs, and recording consumed intents in a committed ledger that keeps cherry-picks and merge-backs between release branches safe. Packages can be moved onto per-package release lanes with the new pnpm lane <name> --filter <pkg> command and back with pnpm lane main --filter <pkg> (pnpm lane shows the membership), releasing X.Y.Z-lane.N prereleases from the same runs that release stable versions of the packages on the main lane. Configuration lives under the new versioning key of pnpm-workspace.yaml (fixed, ignore, maxBump, lanes, changelog). When two workspace projects publish the same name, intent files, versioning.lanes, and versioning.fixed/ignore may reference a project by its workspace-relative directory path (e.g. "./pnpm/npm/pnpm") — the one additive extension to the changesets format, applied automatically by pnpm change.

  Release changelogs default to registry storage (versioning.changelog.storage): no CHANGELOG.md is committed. Each release's section is composed at publish time and packed into the published tarball on top of the previously published version's changelog, and the consumed change intents are garbage-collected by a later pnpm version -r only once the registry confirms the version is published with its section. Set versioning.changelog.storage: repository to keep committed CHANGELOG.md files instead.

• Added a new override selector form with an empty range — "pkg@": "<version>" — called a convergence override. It rewrites a dependency edge only when its exact version satisfies the edge's declared range, so compatible consumers converge on one version while incompatible consumers keep their own resolution — now and for any dependent added in the future #​12794.

  overrides:
    "form-data@": 4.0.6

  The value must be an exact version. When a full resolution detects that every declared range also admits a newer version, pnpm warns that the override is stale and names the version to converge on. Previously an empty range in an override selector was undocumented and behaved like a bare (unscoped) override.

Patch Changes

• A tokenHelper set in the global pnpm auth.ini is no longer rejected as project-level configuration. The guard that blocks tokenHelper from a project .npmrc only treated ~/.npmrc as a trusted source, so a helper written to auth.ini (for example by pnpm config set) failed on every command and could not even be removed with pnpm config delete. A tokenHelper in a workspace or project .npmrc is still rejected.

• pnpm cache delete now removes a package's metadata from every metadata cache directory (metadata, metadata-full, and metadata-full-filtered), instead of only the one the current resolution mode reads. Previously a package cached under a different mode (e.g. metadata-full-filtered) was left behind. Closes #​12753.

• Fixed an injected workspace dependency (injectWorkspacePackages: true) incorrectly staying as file: instead of deduping back to link: when an unrelated, ordinary shared dependency resolved to a peer-suffixed variant for the target project's own copy but not for the injected occurrence. See #​10433.

• pnpm deploy now supports workspaces that use catalogs.

• Fixed pnpm deploy with a shared lockfile so local file: tarball dependencies keep their package name in the generated deploy lockfile. This prevents warm-store deploys from failing with ERR_PNPM_UNEXPECTED_PKG_CONTENT_IN_STORE when the tarball filename includes the version.

• Options that follow create, exec, or test appearing as a subcommand of another command are now parsed instead of being silently treated as positional parameters. For example, pnpm team create @&#8203;org:team --registry <url> previously ignored the --registry option and sent the request to the default registry.

• pnpm add -g, pnpm update -g, pnpm setup, and the self-updater no longer fail with ERR_PNPM_MISSING_TIME when trustPolicy: no-downgrade or resolutionMode: time-based is set in the global config #​12883. The decision to fetch full registry metadata now lives in one place, and the no-downgrade trust policy always requests full metadata (matching the self-updater), since the trust evidence it checks is missing from abbreviated metadata even on registries that include the time field.

• pnpm list and pnpm why no longer crash with EMFILE: too many open files when a project has a large number of unsaved dependencies (packages present in node_modules but not in the lockfile). The reads of those packages are now concurrency-limited.

• The published pnpm package no longer declares dependencies or devDependencies. Because the CLI bundles its runtime dependencies into dist/node_modules, those fields are dropped when packing, so npm install of the tarball no longer tries to resolve internal-only packages such as @pnpm/test-ipc-server. Closes #​12955.

• Fixed pnpm publish --otp and pnpm publish --batch --otp to send the configured OTP to the registry.

• pnpm publish again sends the package's README to the registry as metadata, so registries can render it on the package page. The readme is always included in the published metadata (matching the npm CLI), while the embed-readme setting continues to control only whether the readme is written into the package.json inside the tarball. This restores the behavior that was lost when publishing became fully native. Closes #​12966.

• Fixed the dependency status check wrongly reporting "up to date" when a package.json, .pnpmfile.cjs, or patch file was edited in the same second as the previous install, on filesystems that record mtimes at whole-second resolution (for example ext4 with 128-byte inodes). The optimistic repeat-install fast path and verify-deps-before-run compared mtimes strictly, so a same-second edit whose mtime rounded down looked unchanged and re-resolution was skipped. Such a file's whole second is now treated as possibly-modified, falling through to the content check; behavior on sub-second filesystems is unchanged.

• Retry package metadata requests when a registry or proxy returns 304 Not Modified to an unconditional request, preventing false ERR_PNPM_CACHE_MISSING_AFTER_304 failures pnpm/pnpm#12882.

  If the retry also returns 304, report ERR_PNPM_META_NOT_MODIFIED_WITHOUT_CACHE instead.

• Fixed pnpm update removing transitive lockfile entries when dedupePeerDependents is disabled and the selected package is absent pnpm/pnpm#12456.

• Limit modern deploy lockfiles and localized virtual stores to dependencies reachable from the selected dependency groups.

• A tokenHelper command is now given a 60-second time limit. A helper that hangs (deadlock, stuck I/O) is killed and reported as an error instead of leaving the command waiting forever.

• Fixed orphaned child processes on Windows when pnpm exits on an error while commands spawned by pnpm exec or pnpm dlx are still running (for example, when one project's command fails during pnpm --recursive exec). The PIDs of these commands are now recorded when they are spawned and their whole process trees are terminated with taskkill on an error exit. Previously the cleanup relied on enumerating the system process list, which is so slow on Windows that the enumeration hit its timeout and the cleanup was silently skipped #​12406.

• pnpm pack now respects workspace-root .npmignore and .gitignore files when packing workspace packages.

Platinum Sponsors

Gold Sponsors

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.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

<--- Last few GCs --->

[956:0x3da06000]   170919 ms: Mark-Compact (reduce) 1476.0 (1502.5) -> 1455.5 (1465.3) MB, pooled: 0 MB, 345.16 / 0.00 ms  (+ 1963.4 ms in 103 steps since start of marking, biggest step 39.3 ms, walltime since start of marking 2662 ms) (average mu = 0.349[956:0x3da06000]   173969 ms: Mark-Compact 1455.5 (1465.3) -> 1453.4 (1462.1) MB, pooled: 5 MB, 3050.86 / 0.01 ms  (average mu = 0.185, current mu = 0.000) allocation failure; GC in old space requested

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

 1: 0x74eae8 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/opt/containerbase/tools/node/24.18.0/bin/node]
 2: 0xc42680  [/opt/containerbase/tools/node/24.18.0/bin/node]
 3: 0xc4276f  [/opt/containerbase/tools/node/24.18.0/bin/node]
 4: 0xee5fc5  [/opt/containerbase/tools/node/24.18.0/bin/node]
 5: 0xee5ff2  [/opt/containerbase/tools/node/24.18.0/bin/node]
 6: 0xee62ea  [/opt/containerbase/tools/node/24.18.0/bin/node]
 7: 0xef6fea  [/opt/containerbase/tools/node/24.18.0/bin/node]
 8: 0xefb390  [/opt/containerbase/tools/node/24.18.0/bin/node]
 9: 0x198d931  [/opt/containerbase/tools/node/24.18.0/bin/node]
/usr/local/bin/node: line 18:   956 Aborted                 /opt/containerbase/tools/node/24.18.0/bin/node "$@"

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
evlog-docs	Error		Jul 20, 2026 7:55am
just-use-evlog	Error		Jul 20, 2026 7:55am