Blade (javaabu/forms) and Inertia React (@javaabu/forms) views

Every view ships in both:

Blade with javaabu/forms v2 components
Inertia React (TypeScript) with @javaabu/forms and @javaabu/onu, shipped through javaabu/manifest
Config option to choose the stack; views publishable and overridable
Larger forms defined once with javaabu/stencil
Tests for both stacks

Blade components, stencil field and manifest assets

Done on main. The package's views are the editor field and the content renderer, and both ship in both stacks:

Blade (javaabu/forms v2): <x-block-editor::editor>, <x-block-editor::content>, and one view per block. Publishable (--tag=block-editor-views) and overridable per file.
Inertia React (TypeScript, @javaabu/forms + Onu tokens, shipped through manifest): BlockEditorField, BlockEditor, BlockContent, StencilBlockEditor. Files can be overridden through manifest (resources/vendor/block-editor/js/…).
Tests for both stacks, including shared fixtures that check the Blade and React markup is identical.

Decisions:

No views stack config option. The package has no controllers or pages, so it never chooses a stack. You use the Blade component in Blade and the React component in React. A switch would do nothing.
No stencil form for the block settings. They're generated from the block's Attribute definitions in PHP, so they're still defined once.

Navigation Menu