pnpm and yarn both allow "resolutions" or "overrides", a mechanism for forcing a specific dependency onto a specific version. This includes the ability to point to a fully different package if necessary.
Dependency Checker does not check for these resolutions, leading it to error when it should likely just warn.
For instance using pnpm override like so will fail:
Missing yarn packages:
Package: ember-auto-import
* Specified: ^2.4.2
* Installed: (not installed)
Run `yarn` to install missing dependencies.
Stack Trace and Error Report: /var/folders/51/51f8s9mn649fd4qbcmc998_m0000gp/T/error.dump.c0095d2c4be470061dd809f60478b47b.log
An error occurred in the constructor for ember-cli-dependency-checker at /Users/cthoburn/github/auditboard/auditboard-frontend/node_modules/.pnpm/ember-cli-dependency-checker@3.3.1_ember-cli@4.7.0/node_modules/ember-cli-dependency-checker
ELIFECYCLE Command failed with exit code 1.
pnpm
andyarn
both allow "resolutions" or "overrides", a mechanism for forcing a specific dependency onto a specific version. This includes the ability to point to a fully different package if necessary.Dependency Checker does not check for these resolutions, leading it to error when it should likely just warn.
For instance using pnpm override like so will fail:
with an error like so: