You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The error message for hardhat compile when forge is not installed does not tell users this fact. This could help users debug the build process more easily. The following error is produced:
An unexpected error occurred:
TypeError: Cannot read properties of null (reading 'code')
at analyzeModuleNotFoundError (/home/circleci/project/node_modules/hardhat/src/internal/core/config/config-loading.ts:161:13)
at Environment.run (/home/circleci/project/node_modules/hardhat/src/internal/core/runtime-environment.ts:136:33)
at async main (/home/circleci/project/node_modules/hardhat/src/internal/cli/cli.ts:218:5)
error Command failed with exit code 1.
The text was updated successfully, but these errors were encountered:
"Command failed. Is Foundry not installed? Consider installing via `curl -L https://foundry.paradigm.xyz | bash` and then running `foundryup` on a new terminal. For more context, check the installation instructions in the book: https://book.getfoundry.sh/getting-started/installation.html."
Devs are getting confused by the error message above and I'm trying to think of what is most convenient for an outside contributor when it comes to getting foundry. I don't love the idea of a postinstall hook that uses easyfoundryup if forge isn't in the PATH when calling yarn in the optimism monorepo but that would be convenient
The error message for
hardhat compile
whenforge
is not installed does not tell users this fact. This could help users debug the build process more easily. The following error is produced:The text was updated successfully, but these errors were encountered: