Release 2.5.1
Safer project creation, reliable Git hooks, consistent generators, and scoped pnpm build-script approvals.
Fixed
- Failed dependency installation now exits nonzero, preserves diagnostics, and rolls back new or forced project creation.
- Generated Git hooks stop on lint, staged or unstaged whitespace, and build errors.
- Slice names starting with a number are rejected before any files are written.
- Generic React-family view formatting matches the Next.js template formatter for the audited feature and widget output.
- Interactive stack defaults match each framework's unattended defaults, including native Fetch for Nuxt and SvelteKit.
- The --yes option requires an explicit project name and framework instead of prompting or silently exiting without creating a project.
- New pnpm projects use framework-scoped build-script approvals while preserving existing workspace policies.
Changed
- Regression coverage now includes installation rollback, behavioral Git-hook checks, numeric-leading slice names across all frameworks, and interactive-default parity.
- Framework CI smoke tests generate every slice type plus auth, with additional React and Nuxt build-policy coverage on pnpm 10.26 and 11.
Compatibility
- All five stable frameworks remain supported; the configuration schema stays at version 1.
- The generated pnpm build-script policy requires pnpm 10.26 or later; pnpm 11 requires Node.js 22 or later. Framework-specific Node.js requirements still apply.
- These fixes apply to new project creation and generation. Running the newer CLI does not automatically migrate existing files, hooks, or dependencies. Do not use --force to upgrade a customized project.
Use this version
bash
npx create-fsd-architecture@2.5.1Running a newer CLI does not migrate an existing project's files or dependencies. Review compatibility notes before generating new slices.