migration-setup

To scaffold a 2nd-gen web component migration, this automation creates the core SWC directory structure and generates stub files for export wiring. This establishes a build-ready baseline before any implementation work begins.

Wiring up exports during migration is automated by generating stubbed files alongside the core directory structure. This ensures components are importable and enables a build pass during Phase 2 of the migration process.

You need to set up stub files during Phase 2 of a 1st-gen to 2nd-gen migration. Establishing this build-ready baseline before implementation guarantees a consistent foundation and a clean starting point for development.

Yes, you can verify your build passes before implementation by creating the core skeleton for the target component and running the recommended Phase 2 workflow. This ensures the scaffolded structure is fully build-ready.

No, this scaffolding tool does not require existing export configurations. It generates the necessary stubbed files and wires up exports automatically to ensure the component is importable from the start.

Phase 2 migration requires a specific directory structure to ensure a consistent foundation across components. Scaffolding the core SWC directories and wiring exports establishes a standardized, build-ready environment for development.