What problem does it solve?
Building a Webiny extension that spans both the API (Lambda) and Admin (browser) runtimes requires coordinating two separate entry points, a shared domain layer, and build-time configuration — mistakes in registration or imports cause build failures or missing DI containers at runtime.
Core Features & Use Cases
- Extension Skeleton: Defines the package structure with
shared/, api/, and admin/ directories plus a top-level component registering <Api.Extension> and <Admin.Extension> entry points.
- Registration Rules: Enforces correct use of
src props with full file paths, export default for entry-point files, and prohibits mounting admin/api code outside entry-point components.
- BuildParam Configuration: Declares
<Api.BuildParam> and <Admin.BuildParam> inside the extension component so configuration flows from webiny.config.tsx into both runtimes without using process.env in deployed code.
- Use Case: Create a lead-management extension where the API side handles GraphQL and domain logic in Lambda while the Admin side renders UI in the browser, sharing entity types and constants from one package.
Quick Start
Ask the AI to scaffold a new full-stack Webiny extension with API and Admin entry points, a shared domain layer, and BuildParam declarations.
