Skip to content
Postkit

Reference

Troubleshooting. Diagnose provider, theme, routing, hydration, directive, and remote metadata integration issues.

Components render with only host styling

This is the default. Postkit inherits the host Chakra system and does not apply its visual preset automatically. Pass preset={postkitDefaultTheme} for the standalone appearance, register Postkit slot recipes in the host system, or use theme={createPostkitTheme(...)} for deliberate scoped overrides. The article must still render beneath PostkitProvider so Chakra context is available. CodeBlock, CodeGroup, and Terminal retain semantic structural styling in this mode, but their opinionated dark palettes belong only to the standalone preset.

Use the framework adapter rather than the base React MDX map. Render the article beneath the router provider and verify that the destination is considered an internal URL by the adapter.

A plain Markdown directive is ignored

Enable Postkit's Remark plugins and use the postkit- directive name. Use JSX instead of directive brace syntax inside MDX files.

Astro hydration fails

Confirm that the React and MDX integrations are enabled and that a custom Chakra system is exported from a module addressable by both server rendering and hydrated islands.

Run the resolver on a server or at build time. Check the provider configuration, URL policy, response contract, and cache independently from the rendering component.

When reporting an issue, include the Postkit package version, framework and runtime versions, a minimal content sample, and whether the failure occurs at build time, server rendering, hydration, or client interaction.

Edit this page on GitHub

Postkit

Richer posts, written once, right everywhere.

© 2026 Postkit. MIT licensed.
LicensingPrivacy