Angular Flex-Layout Codemod

Angular Flex-Layout Codemod is a review-first CLI for migrating supported Angular Flex-Layout template directives to Tailwind CSS v4 or native CSS. Version 2 remains a prerelease.

Plan first. Review unresolved cases. Write only when you are ready.

The codemod changes only cases for which it can produce a supported equivalent. When it cannot prove that boundary, it leaves the source in place and reports a diagnostic instead of guessing.

Read the detailed documentation, or try a single template in the separate browser playground.

Requirements and installation

The CLI requires Node.js 22.12 or newer (tested on Node 22 and 24). This runtime can differ from your legacy Angular build runtime; the codemod reads source without loading the application dependencies. Install the current beta as an exact development dependency so your package manifest and lockfile retain the reviewed version:

npm install --save-dev --save-exact @nipe-solutions/flex-layout-codemod@beta

See Installation and requirements for the project-baseline checklist.

Plan, review, write

Create a plan and an optional JSON report without changing project templates or stylesheets:

npx flex-layout-codemod ./src --target tailwind --tailwind-stylesheet ./src/styles.css --plan --report ./reports/flex-layout.json

The Tailwind stylesheet is optional. Supplying it lets the codemod respect a project-specific v4 prefix and breakpoint configuration. See target configuration, responsive mapping, and the safety model.

Review the proposed output and every unresolved diagnostic. The report is the command's intentional filesystem output in plan mode.

Apply the reviewed Tailwind CSS plan explicitly:

npx flex-layout-codemod ./src --target tailwind --tailwind-stylesheet ./src/styles.css --write

For native CSS output, target limits, output paths, and recovery behavior, follow the migration workflow. Keep the migration on a clean branch and review the resulting diff and application tests.

Documentation

• Migration guide
• Compatibility by target and directive
• Diagnostics and remediation
• Complete CLI reference
• JSON reports and CI
• Safety, transactions, and recovery

Contributing and support

Read CONTRIBUTING.md before opening a pull request. Use GitHub Issues for reproducible, redacted migration cases. Report vulnerabilities only through GitHub private vulnerability reporting; see SECURITY.md and support guidance.

Maintainers should follow the reviewed release process.

License

MIT