[CharanMN7]

Adds a supported way for a site to register its own MDX components. The site that hit this, an Astro 7 site on @inkform/astro 0.1.0, faked a "screenshot slot" with the kit's <Frame> around a plain <div> plus CSS, because there was no way to add a component.

components option

inkform({ components: './src/mdx-components.tsx' });

• Every export whose name starts with a capital letter can be used in any MDX page without an import. Entries of a default-exported object (export default { Screenshot }) work too.
• They are merged over the kit's, so a site can add <Screenshot> or replace <Frame>. Unknown names still render the kit's visible fallback.
• They render in the same build-time React pass as the kit. Image srcs and links they print get Astro's base, like the rest of the content (from fix(astro): Astro's base in every link, llms.txt trailing slashes, phone header #29). The docs pages still ship no React. The existing e2e test covers that.
• Exports that aren't components (helpers, constants) are ignored. A missing module fails the build at config time with its path.
• Served through a virtual:@inkform/astro/components module, so Vite handles it like any other source file. Edits show up on reload in astro dev.

JSX without @astrojs/react

Astro's tsconfig preset sets "jsx": "preserve", and only a UI integration sets up JSX compilation. A .tsx components module in a site without one failed with "JSX syntax is disabled". When the module is .jsx/.tsx, no React, Preact, Solid or Vue integration is installed, and the site hasn't set vite.oxc.jsx, the integration now sets Vite's oxc.jsx to React's automatic runtime. That only affects .jsx/.tsx files, which such a site can't use anywhere else. needsReactJsx() makes the decision and has unit tests.

Docs and example

• README: the option in the table, plus a "Your own components" section covering wrapping kit components from @inkform/framework/components, overrides, the JSX note and the base-path behaviour.
• examples/astro-docs registers src/mdx-components.tsx (<Screenshot>, styled through customCss). The components page uses it, and an e2e test checks it renders.
• An Unreleased CHANGELOG entry is added. No version bump.

Test plan

• npm test --workspace=@inkform/astro: 72 pass. New tests cover option resolution, the virtual module source, userComponents() (memo/forwardRef, default object, ignoring non-components), rendering with a kit override and the fallback kept, and needsReactJsx().
• npm run typecheck for @inkform/astro and the example: 0 errors.
• npm run test:e2e --workspace=@inkform/example-astro-docs: 36 pass.
• A throwaway site with no @astrojs/react and a plain astro/tsconfigs/strict tsconfig, not committed, with base: '/ig' and trailingSlash: 'always'. Its .tsx module wraps the kit's Frame.
  • Before the JSX change, the build failed to parse the module. After it, astro build renders the component inside fw-frame.
  • astro dev serves it and picks up an edit to the module on the next request.
  • astro check reports 0 errors.

🤖 Generated with Claude Code

https://claude.ai/code/session_011YQ6fJxGHg3CxGkTzw6Yhc

[vercel]

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

2 Skipped Deployments

Project	Deployment	Actions	Updated
framework-inkform-docs	Skipped		Oct 27, 2026 8:46am UTC
pokeapi	Skipped		Oct 27, 2026 8:46am UTC