Ember CLI TypeScript Blueprints is an Ember CLI addon designed to provide TypeScript-aware blueprints for generating standard Ember CLI entities, including those for `ember-source` and `ember-data`. This package, currently at version 3.0.0, historically filled a crucial gap by enabling developers to generate TypeScript files within Ember applications before native Ember CLI support for TypeScript blueprints was available. However, the project was archived in December 2022 and is no longer maintained, as recent versions of Ember CLI (starting from Ember 4.8.0 with RFC 0724 and 0800 implementations) now offer integrated, first-party TypeScript blueprint generation. Consequently, this addon is effectively abandoned, and new Ember projects or migrations should leverage Ember's native TypeScript capabilities. The package had an irregular release cadence, with its last major update seven years ago, reflecting its deprecation in favor of core framework features.
npm install ember-cli-typescript-blueprintsVerified import paths — ran on the pinned version, not inferred.
Demonstrates the historical installation and usage of the addon's CLI commands to generate TypeScript-aware Ember entities.
Remove `ember-cli-typescript-blueprints` from your project. For new projects, use `ember new my-app --typescript`. For existing projects, configure `ember-cli-babel` for TypeScript and use `ember generate <entity> --typescript` where available, or manually create `.ts` files and configure `tsconfig.json`.
Migrate away from `ember-cli-typescript-blueprints` and `ember-cli-typescript` to leverage Ember's native TypeScript support. Ensure your `types/<your-app>/index.d.ts` file correctly imports `ember-source/types` and `ember-source/types/preview` if desired, and remove incompatible `@types` packages.
If maintaining an older project using `ember-cli-typescript` v1, review the migration guide to v2, specifically addressing `const enum` usage and Babel configuration changes. Consider upgrading to native Ember CLI TypeScript support if possible.
Ensure `@types/ember-data` (if applicable for your Ember version/setup) is installed. Verify your `types/<your-app>/index.d.ts` file properly extends the `ModelRegistry` for Ember Data models. For modern Ember, ensure you're using official types and correctly extending type definitions.
For each of your Ember Data models, ensure you add code to extend the `ModelRegistry` in your `types/ember-data/ember-data.d.ts` (or similar) file. Example: `declare module 'ember-data/types/registries/model' { export default interface ModelRegistry { 'my-model': MyModel; } }`Try clearing your npm/yarn cache (`npm cache clean --force` or `yarn cache clean`). Delete `node_modules` and `package-lock.json` (or `yarn.lock`), then reinstall. If it's a permission error, ensure proper directory permissions or run with `sudo` (use cautiously).