crytic / crytic/crytic-compile
Fix detection of node_modules/ in monorepos
- Dominant language
- Python
- Stars
- 197
- Forks
- 97
- PR merge metrics
- No merged PRs in 30d
Description
We need a way to find node_modules for monorepo that is more robust
This is especially sticky for monorepo projects where something like `@openzeppelin/*` is not installed in the relative `node_modules/` but in the root workspace. Yarn 2 removed nohoist as well, so I haven't really found a good solution to this yet.
A temporary workaround is to symlink the relevant packages into the relative/workspace's `node_modules/` dir but that gets pretty annoying and is temporary.
ETA: A solution is adding the following to the `package.json` for the contract package:
"installConfig": {
"hoistingLimits": "dependencies"
},
_Originally posted by @mikeshultz in https://github.com/crytic/slither/issues/852#issuecomment-1112361513_
Contributor guide
Assessment
This issue has not been assessed yet.