rebase! chore(deps): update nuxtjs monorepo to v4.4.5

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@nuxt/kit (source)	4.3.1 → 4.4.5
nuxt (source)	4.3.1 → 4.4.5

---

Release Notes

nuxt/nuxt (@​nuxt/kit)

v4.4.5

Compare Source

4.4.5 is the next patch release.

👉 Changelog

compare changes

🔥 Performance

• kit: Cache layer roots and short-circuit isIgnored relative (#​35015)

🩹 Fixes

• vite: Resolve vite clientServer with ssr: false (#​34959)
• nitro: Correct payload route rule for / + override ssr: true (#​34990)
• nitro: Break recursive rendering deadlocks during prerender (#​34939)
• vite: Drop redundant css link when entry styles are inlined (#​34950)
• vite: Sort optimizeDeps.include in pre-bundle hint (#​34976)
• nuxt: Only force suspense remount after first resolve (#​34949)
• kit: Read .env before resolving nuxt schema (#​34958)
• nitro: Preserve serverHandlers array after nitro:config (#​34985)
• nuxt: Cast partial nitro handlers when prepending to server arrays (61dcde4db)
• vite: Only consider CSS inlined when styles are actually emitted (#​35006)
• nuxt: Dedupe getCachedData for concurrent callers sharing a key (#​34999)
• nuxt: Respect factory fetch/baseURL options in server useFetch (#​35003)
• nuxt: Handle string presets in auto-imports (#​35013)
• nuxt: Correct island transform for server pages and 'deep' mode (#​35005)
• vite: Inline css for non-island children of server components (#​35001)
• nuxt: Defer head DOM updates until page transition finishes (#​35016)
• nuxt: Explicitly freeze head during island plugin phase (#​35010)
• vite: Inline css imported from non-vue js modules (#​35020)

📖 Documentation

• Add warning about routing in server components (#​34994)

🏡 Chore

• Fix lockfile (c3ee07801)
• Pin jiti (c8102228f)
• Lint (39422b6d2)
• Pin @vue/compiler-sfc (cd404a14c)
• Ignore pnpm cyclic workspace deps warn (#​34998)
• Remove jiti from build steps (#​35004)

✅ Tests

• Extract server components fixture + add some failing tests (#​34995)
• Isolate buildDir per matrix project for shared fixtures (#​35007)
• Remove tests for 5.x runtimeBaseURL fature (816c25487)

❤️ Contributors

• Daniel Roe (@​danielroe)
• Harlan Wilton (@​harlan-zw)
• Jonazzzz (@​Bombastickj)
• Damian Głowala (@​DamianGlowala)
• Florian Heuberger (@​Flo0806)

v4.4.4

Compare Source

v4.4.2

Compare Source

v4.4.1

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

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

---

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

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
nuxt-better-auth-docs	Ready	Preview, Comment	May 12, 2026 6:34am

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	better-auth	e87c4b7	May 12 2026, 06:31 AM

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@onmax/nuxt-better-auth@347

commit: e87c4b7

[onmax]

@renovate rebase

[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

Scope: all 3 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 44, reused 0, downloaded 1, added 0
Progress: resolved 59, reused 0, downloaded 1, added 0
Progress: resolved 60, reused 0, downloaded 1, added 0
Progress: resolved 61, reused 0, downloaded 1, added 0
Progress: resolved 132, reused 0, downloaded 1, added 0
Progress: resolved 203, reused 0, downloaded 1, added 0
Progress: resolved 277, reused 0, downloaded 1, added 0
Progress: resolved 357, reused 0, downloaded 1, added 0
Progress: resolved 439, reused 0, downloaded 1, added 0
Progress: resolved 559, reused 0, downloaded 1, added 0
Progress: resolved 653, reused 0, downloaded 1, added 0
Progress: resolved 702, reused 0, downloaded 1, added 0
Progress: resolved 730, reused 0, downloaded 1, added 0
Progress: resolved 890, reused 0, downloaded 1, added 0
Progress: resolved 943, reused 0, downloaded 1, added 0
Progress: resolved 984, reused 0, downloaded 1, added 0
Progress: resolved 1140, reused 0, downloaded 1, added 0
 WARN  Request took 11398ms: https://registry.npmjs.org/vite
Progress: resolved 1167, reused 0, downloaded 1, added 0
Progress: resolved 1200, reused 0, downloaded 1, added 0
Progress: resolved 1251, reused 0, downloaded 1, added 0
Progress: resolved 1299, reused 0, downloaded 1, added 0
Progress: resolved 1316, reused 0, downloaded 1, added 0
Progress: resolved 1408, reused 0, downloaded 1, added 0
 WARN  Request took 23988ms: https://registry.npmjs.org/@prisma%2Fclient
Progress: resolved 1421, reused 0, downloaded 1, added 0
/tmp/renovate/repos/github/nuxt-modules/better-auth/playground:
 ERR_PNPM_TRUST_DOWNGRADE  High-risk trust downgrade for "semver@6.3.1" (possible package takeover)

This error happened while installing the dependencies of @better-auth/cli@1.5.0-beta.13
 at @babel/core@7.29.0

Trust checks are based solely on publish date, not semver. A package cannot be installed if any earlier-published version had stronger trust evidence. Earlier versions had provenance attestation, but this version has no trust evidence. A trust downgrade may indicate a supply chain incident.

[onmax]

@renovate rebase

[onmax]

@renovatebot rebase