[BUG] "sill idealTree buildDeps" takes a lot of time a project with workspaces

[midudev]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

After executing npm install the sill idealTree buildDeps step takes a long time (minutes) causing npm@7 working with workspaces slower than npm@6 installing projects separately.

It seems that is fetching packages sequentially instead using parallelization.

Vídeo with the demo:

CleanShot.2021-05-18.at.16.07.23.mp4

Expected Behavior

npm install on npm@7 with workspaces takes less time than npm@6 installing manually each workspace.

Steps To Reproduce

1. In a environment with a lot of dependencies and workspaces.
2. With this config:

  "workspaces": [
    "domain",
    "icons",
    "literals"
  ],

3. Run npm install
4. See that the step buildDeps take longer than expected.

Some considerations:

• We're using some npm private packages on our package.json.
• Workspaces are dependencies of root project as well.

More info:
On Travis, builds using npm@6 and installing workspaces manually takes 90s.
Using npm@7 it takes 170s using a single npm install.

Environment

• OS: macOS 11.3.1
• Node: 16.1.0
• npm: 7.17.0

[midudev]

I can't provide a example project as it's a commercial project with full of private dependencies but If there's some log or something I could try to give you, feel free to tell me how to extract it.

[midudev]

Tried latest version 7.17.0. Still happening.

[kumarrishav]

I am still facing the slowness on latest npm v7 and v8

[vdawg-git]

What helped me was to completely uninstall node and then to reinstall it with nvm.
However, I dont know if this is going to happen again.

Edit: Okay, it happens again.

[midudev]

@V-Dawg this is happening in Travis as well. I think it's something related with the way of resolving the tree.

[EduApps-CDG]

Tried with yarn and npm (v8.1.4 and v8.3.0), also the same thing happens.
But it's working on 7.19.1

[EduApps-CDG]

This bug is critical for me. It's so slow that causes ETIMEDOUT even on a empty project.

Update:

After running for a while, npm returns:

npm ERR! code ETIMEDOUT
npm ERR! syscall connect
npm ERR! errno ETIMEDOUT
npm ERR! network request to https://registry.npmjs.org/natural failed, reason: connect ETIMEDOUT 2606:4700::6810:1223:443
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/eduardo/.npm/_logs/2021-12-11T07_56_48_769Z-debug.log

But when I go to https://registry.npmjs.org/natural, it loads pretty fast, so I don't think it's a network problem.