You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use the @nx/webpack:webpack executor with the generatePackageJson option, the resulting package.json file doesn't include any dependencies that are defined with package aliases.
Here's an example of a package.json file with a package alias:
It isn't similar. I believe that issue happens because TypeORM doesn't have a direct dependency on mssql, so Nx can't infer that mssql belongs in the generated package.json file.
In this issue, the app code explicitly uses the dependency with a package alias, but that dependency still isn't added to the generated package.json file.
Current Behavior
When I use the @nx/webpack:webpack executor with the
generatePackageJson
option, the resulting package.json file doesn't include any dependencies that are defined with package aliases.Here's an example of a package.json file with a package alias:
I have reproduced this issue with PNPM v8 and NPM. The repro repository uses NPM.
Expected Behavior
I expect the generated package.json file to include all the dependencies used in the project, including those with package aliases.
GitHub Repo
https://github.com/stephenwade/nx-issue-repro-scaling-carnival
Steps to Reproduce
npm ci
npx nx build
Nx Report
Failure Logs
No error messages are reported. It just produces an incorrect result.
Package Manager Version
npm 10.8.2
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: