Analyze dependencies of an Ember project
Both Embroider and pnpm ask that packages declare their dependencies correctly. The codemod (really, a linter) performs a static code analysis so that you can easily find missing and unused dependencies.
For more information, see Fixing Package Dependencies.
Step 1. Run the codemod (e.g. at the workspace root of a monorepo).
cd <path/to/your/project>
pnpx analyze-ember-project-dependenciesStep 2. Check the output for true positives.
Optional: Specify the component structure
By default, apps and addons follow the flat component structure for components. Pass --component-structure to indicate otherwise.
pnpx analyze-ember-project-dependencies --component-structure nestedOptional: Specify the project root
Pass --root to run the codemod somewhere else (i.e. not in the current directory).
pnpx analyze-ember-project-dependencies --root <path/to/your/project>The codemod is designed to cover typical cases. It is not designed to cover one-off cases.
To better meet your needs, consider cloning the repo and running the codemod locally.
cd <path/to/cloned/repo>
# Compile TypeScript
pnpm build
# Run codemod
./dist/bin/analyze-ember-project-dependencies.js --root <path/to/your/project>Important
The codemod uses a list called KNOWN_ENTITIES to analyze implicit code. The list accounts for packages that live outside of your project. It isn't meant to be (and doesn't have to be) exhaustive.
You can modify KNOWN_ENTITIES to get more accurate results.
src/utils/find-entities/known-entities.ts
const KNOWN_ENTITIES = new Map<PackageName, Partial<ProjectDataEntities>>([
[
'@ember/render-modifiers',
{
modifiers: ['did-insert', 'did-update', 'will-destroy'],
},
],
// ...
]);- Node.js v22 or above
See the Contributing guide for details.
This project is licensed under the MIT License.