Extension scans `node_modules` in nested repos causing significant lag

[smol-ninja]

Problem

The extension ignores node_modules at the root level but scans Solidity files in node_modules of nested/child repos.

root/
├── node_modules/          ← ignored ✓
└── src/
    └── node_modules/      ← scanned ✗ (causes lag)

As a result of this, vscode/cursor becomes unresponsive when working in a monorepo with nested node_modules. If you disable the extension or delete nested node_modules, the lag disappears.

Suggested Fix

Ignore **/node_modules/** recursively rather than just root-level node_modules.

Example Repo

https://github.com/sablier-labs/lockup/tree/staging (foundry monorepo with multiple nested foundry.toml)

Screenshots

See #722 (comment) below.

[kanej]

Hey @smol-ninja, could you paste the Solidity output you are getting:

When I run in codespaces my navigation didn't slow down after 30-60 seconds. Though there are lots of `Source "xxx" not found: File not found." errors. So there is something going wrong in import resolution - but I am unsure if that is related.

[smol-ninja]

could you paste the Solidity output you are getting

I have different output than yours. In my case, it finds 13,547 solidity files. Can you please run the following commands to install dependencies and then test it again:

bun install
just install-all

My guess is that the extension is also scanning solidity files from node_modules (confirmed, if I delete node_modules then the lag disappears).

Though there are lots of `Source "xxx" not found: File not found." errors

That is because you didn't install dependencies. If you run the above commands, they should go away.

[smol-ninja]

I have updated the OP given that I have found the root cause.

[smol-ninja]

Any thoughts @kanej? Its a critical problem for us.

[smol-ninja]

Hi @kanej, @antico5, any thoughts on when this can be fixed? Its slowing down productivity.

[kanej]

Hey @smol-ninja, sorry we are taking so long in getting to this - Hardhat 3 is pulling in most of our attention.
I am aiming to take a look towards the end of the week, and will hopefully have more to report.

[smol-ninja]

Any update @kanej?

[PaulRBerg]

Thanks @kanej - this is a major blocker to development for our new monorepo, for both us and our auditors. It would be really great if you could have a quick look in case it's an easy fix 🙏

[kanej]

Hey @smol-ninja, I agree with the analysis.
It looks like the extension is misidentifying top level projects (so those it should analyse and build def/use navigation trees for) within node_modules.
We intentionally exclude them for Hardhat projects were node_modules is expected, but the bug is likely we don't have the exclusion in place for Foundry projects - but sablier uses Foundry projects installed from node_modules.