Skip to main content
Browse docs

Marwes documentation

Troubleshooting

Diagnose missing styles, provider wiring, imports, SSR, fonts, and partial CLI setup.

Common setup failures

No styling

Import from the adapter root. It loads the static preset CSS; do not add a second stylesheet.

Provider at the wrong level

Render MarwesProvider once above every Marwes component.

Wrong import

Use @marwes-ui/react, @marwes-ui/vue, or @marwes-ui/svelte — never a different adapter or a deep path.

Theme values are empty

CSS references such as var(--mw-*) resolve only inside the provider boundary. Use useTheme() when JavaScript needs resolved values.

Light/dark flash during SSR

Install the framework theme script before hydration and keep the server and client preference policy aligned.

Fonts blocked by CSP

Allow the configured font origin or self-host the selected font. Keep font loading consistent with the CSP.

Peer version mismatch

Check the adapter package peerDependencies and align framework and renderer versions.

Partial CLI setup

Follow the printed provider example, then rerun pnpm dlx @marwes-ui/cli doctor --run-build. An init result labelled manual-action-required uses exit code 2; command failures can also preserve an underlying exit code 2, so read the printed status.

pnpm dlx @marwes-ui/cli doctor --run-build