MugatuAIMugatuAI Support Hub

Operations

Troubleshooting & build status

Current serving health, the most recent build outcomes, and the fixes that resolve Vite / TanStack Start unloadable dependency failures.

App serving status

Checking the running app…

Recent builds

  • PassingLatest build

    Client, SSR and worker bundles built clean.

    No action needed.

  • FailedPrevious build

    [UNLOADABLE_DEPENDENCY] Could not load node_modules/entities/escape (via parse5).

    Removed a stale `entities` alias from vite.config.ts so parse5 resolved its own v6 copy.

Common fixes: unloadable dependency errors

Stale resolve.alias entry

Symptom: Could not load node_modules/<pkg>/<subpath> — the subpath exists in a newer major.

  1. 1.Open vite.config.ts and look for a bare alias like `pkg: path.resolve(...)`.
  2. 2.A bare alias collapses every nested copy onto one version, so subpath exports added in later majors disappear.
  3. 3.Delete the alias and let the bundler resolve the nested node_modules copy.

Version mismatch between hoisted and nested copies

Symptom: One dependency needs ^6, another pins 4.x, and the import path only exists in 6.

  1. 1.Inspect the requiring package's dependency range and the hoisted version.
  2. 2.Confirm the nested copy exists (it usually does) before touching versions.
  3. 3.Only bump the shared dependency if no nested copy is present.

Missing module or package

Symptom: Cannot find module '...' during transform.

  1. 1.Install the package first, then add the import in the same change.
  2. 2.For local modules, create the file before importing it — there is no runtime fallback.
  3. 3.Route files must exist before any typed Link or navigate targets them.

Browser-only library pulled into SSR

Symptom: window is not defined, or document is not defined during prerender.

  1. 1.SSR evaluates imports even inside client-gated components.
  2. 2.Load the library with a dynamic import after hydration instead of a static import.
  3. 3.Keep shared constants and types in a separate browser-safe module.

Node-only package in a server function

Symptom: [unenv] X is not implemented yet, or __dirname is not defined.

  1. 1.The server runtime is a worker, not a full Node host.
  2. 2.Swap the package for a pure-JS, fetch-based or WASM alternative.
  3. 3.Never set ssr.external or resolve.external for the server environment.

Still stuck?

Send the exact output to support and it arrives with the build status already attached.