Open work933k opened 7 months ago
@work933k is it possible to provide a link to your repo?
not without losing my job ;-)
Running into the same with a migration from nx 16 to 17. And same as @work933k , I cannot share the repo. And unfortunately it's something unique as we have other areas with nx 17 and nx 18 and those run fine. Any ideas for how to profile it so we can give you some additional information?
Context I can share:
The generated environment.js in the healthy apps (and same repo pre nx 17) are around 3-6MB. The slow repo is generating 214MB
Checking that file. The 3 variables are
So it's something in that area...
Current Behavior
I'm doing a trial NX upgrade from v16.3.2 to v18.2.1 and notice that doing
npx nx dep-graph --file=dist/dep-graph/dep-graph.html
has become much slower. It now takes over 7 minutes, while it used to take 4 seconds.Expected Behavior
I would not expect such a significant increase of time.
GitHub Repo
No response
Steps to Reproduce
1.
Nx Report
Failure Logs
No response
Package Manager Version
npm v9.5.1
Operating System
Additional Information
WSL2. I'll try to gather more info and it to this issue.
As you can see below it takes 7minutes to generate the HTML. To generate a json file takes less than 1second. Something wierd is going on...
If i run
NODE_DEBUG=* npx nx dep-graph --file=dist/dep-graph/dep-graph.html
then i see no output for a long time after this:I just noticed that the generated environment file is 150mb big:
In the environment.js file is see a continuous repetition of stuff which comes from the nx.json. This is a part of what is see:
And that for all targets and for each of the 100 projects.
Is that as expected?