@nrwl/nest build generates no package.json despite using the "generatePackageJson" option
See original GitHub issueCurrent Behavior
When running the shipped build script, it doesn’t include the required dependencies. It only lists tslib in there, and thus the app crashes when trying to run it outside of my local node_modules context.
Steps to Reproduce
Generating a Nest app using the @nrwl/nest library. I tried with some changes to project.json and a completely untouched default generated app, both produce the problem.
Environment
Windows 10.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Generate package.json on nx build / deployment
I've tryed to use "generate-package-json-webpack-plugin" to generate the package.json, but it only detect half the dependencies. I've also tried ...
Read more >Nx/community - nrwl - Gitter
Hello, is there any way to generate package.json per app? ... When to use [nx g @nrwl/nest:application] and [ng g @nrwl/nest:lib]? what are...
Read more >package.json - npm Docs
Description. This document is all you need to know about what's required in your package.json file. It must be actual JSON, not just...
Read more >package.json | pnpm
For instance, the following package.json in a workspace will create a ... If all projects in the monorepo use the same version of...
Read more >@nrwl/node:webpack | Nx
@nrwl/node:webpack. Node application build target options for Build Facade. Options can be configured in project.json when defining the executor, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Glad that I wasn’t going insane! I suppose this won’t be an issue in the future where I would use the newer version instead by default. Still very strange issue.
I also named my NestJS app
apiand I had the same problem with NX version14.8.2, but updated to14.8.4usingnx migrate latestand that fixed it 🚀