nx: "generatePackageJson" does not include dependencies from `libs/*`

In case it helps anyone else, my solution to this issue was a bit different.

The build executor is @nrwl/webpack:webpack for me and @nrwl/webpack was missing from my devDeps in package.json. Somehow it was still building to dist/, but without the correct deps. npm i -D @nrwl/webpack fixed things.

I ran into this issue and it turns out I had a dependency listed in both devDependencies and dependencies in my package.json, I must have pasted them there by accident, or inadvertently add a -D or something.

However, once I removed them from the devDependencies section my generated package.json had everything it was supposed to!

I had the exact same problem with the dotenv package missing from the generated package.json file when using the option generatePackageJson.

Removing the dotenv package from the devDependencies part of the root package.json solved the problem.

I needed this functionality as well and accomplished it by writing my own executor. Within an executor you can do:

import { readCachedProjectGraph } from "@nrwl/devkit";
const { dependencies } = readCachedProjectGraph();

and the dependencies variable will have everything you need to populate dependencies from libs/*. To see the bulk of logic for how generatePackageJson works you can refer to this file. I would submit a PR but I don’t have the time, but I needed the same thing and accomplished it this way.

Thanks @svaterlaus that worked for me! @nwrl/webpack was in node_modules because it was a dependency of another module (I guess), but installing it explicitly resolves my issue. I had none of my nest project dependencies in the generated package.json file and now it’s OK! 👍

@vsavkin @jeffbcross ‘generatePackageJson’ is not found in schema in latest would you have a solution to this? Seems like it’s not documented in anywhere.

Has anyone found any solutions for that?

Hi all, the original scenario (about dotenv) seems to have been solved already (I can’t reproduce it with the issue author’s reproduce step).

• Create a new workspace
• Generate a NestJS application with nrwl/nest:app
• Generate a library with nrwl/nest:lib
• Use a dependency in the library (eg: dotenv)
• Use the library in the app
• Run npx nx build app with generatePackageJson: true
• dist/apps/app/package.json does have dotenv as one of the dependencies.

`LibModule` uses `date-fns` `BuildableLibModule` uses `dotenv` Both are imported in `AppModule` Both dependencies show up in `dist/apps/api/package.json`

If anyone runs into a similar issue, please share your reproduce steps.

In my case there were 2 problem:

1. I had my peerDependencies so I moved them to dependency and it worked like charm

2. One of my dependencies itself had peerDependencies

Example: My package.json

@celo-tools/celo-ethers-wrapper’s package.json

Solution: Explicitly import peerDependency

Make sure you updated to the current version of the executor(s).

For example @nrwl/node:build executor is replaced with @nrwl/node:webpack and supports generatePackageJson option (source code for schema).

A few of them were renamed here: https://github.com/nrwl/nx/pull/9086

That said, I still have the issue outlined in the initial issue, and even with some packages that are not part of my code base they aren’t being picked up in a nest project despite being directly imported in non-unit test code paths.

I’m facing a similar issue. I generated a publishable lib that uses a MUI component but the generated package.json does not include the required dependencies.

Here is a repo with the minimal setup:

• https://github.com/oncet/nx-playground

What I’m missing?

Update

Finally solved it https://stackoverflow.com/questions/73293762/nx-missing-dependencies-on-generated-package-json/73306728#73306728

Thanks for the clarifications.

1. I feel like Nx can (and should) make this case work but it can be a different issue.
2. For sure, please feel free to tag me in the issue you’re talking about here and we’ll be on it

As for this issue, I’ll leave it open for a bit longer to see if anything comes up. Thanks again for your time

@nartc sorry; I haven’t been actively developing a NX project lately and since have switched to Vite and Turborepo, however, may consider converting back to Nx as Turborepo docker builds are insanely slow when “pruning” dependencies. My NX project I have in production uses webpack plugins to create pruned package.json files, so it’s great to see that this may work out of the box now.

It happened to me and I found out that the missing module is not added to the root package.json. I cleaned the node_modules and reinstall all the dependencies and it’s working now.

I face same issue. Anyone has solution for this issue?. so for now, I must copy root package.json for each project to handle missing modules

Alright well I didn’t have to use a custom executor, all my deps are working now.

I’m guessing at one point the problematic dependencies were a devDependency in my root package.json and the project graph didn’t want to detect that.

NX_CACHE_PROJECT_GRAPH=false nx build api --clear-cache

Would be curious if this helps anyone else assuming you’re on latest nx and using the correct executors. It’s working for me with node:webpack

I need to control versioning on explicit application for allowing different versions on each build. For allowing me push different distributions to different pops.