Adding node dependencies includes a lot of unnecessary contracts

In our use case, one of our contract packages depends on another contract package. However, copying this dependency into the coverage environment results in a ridiculous number of extra contracts being instrumented, due to the inclusion of the dependency’s node modules.

The full list of contracts being instrumented in that repo: https://gist.github.com/sohkai/459dc9ab1b3a410e9af6ab9ae07a196c.

It would be great if we had a way to target certain folders or files in the dependencies for instrumentation, and a way to skip the rest of node_modules.

[cgewecke]

This should be a non-issue with newly published 0.7.0. We’re no longer copying any packages & the tool runs at the same layer as the project root.

However if you run into any weird issues using Lerna with the new version, please just lmk.

A monorepo called Sabiler has been able to run the new version without serious problems so hopefully everything’s ok.

[sohkai]

@sohkai Yes 6.4.5-sc.3 might actually make a difference, I saw some staticcall stuff clear up on the bancorprotocol contracts with that change yesterday.

Can confirm wit sc.3 that these staticcall tests are working for us now as well 👍.

Will check out the gas check in CI! That looks super cool 😃. Quick question on it; how well does it support monorepo tests? Should it try and pipe the results of each separate package together, kind of like what happens with lcov?