-
Notifications
You must be signed in to change notification settings - Fork 362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add forge-std and ds-test as NPM modules for Hardhat backwards compatibility #39
Comments
I'm transferring this issue to Forge Std, since it should happen in that repository - can you also open up a related issue in https://github.com/dapphub/ds-test/? We do not have write permission to that repository 😄 |
I've published a version on NPM, you can import it in a hardhat project too (sharing if that is useful). |
Closing as duplicate in favor of #170 as we no longer depend on |
Component
Forge
Describe the feature you would like
Issue described in detail here.
Many of use would like to use Foundry + Hardhat, which still has tons of use cases (integration testing, complex deployment scripts, etc) and should really not be treated as a direct competitor. However, there are some small inconveniences that we have found when trying to do this.
As shown in the issue, it can almost be tidied up into one source of truth for all dependencies by mapping the paths the Forge uses to
node_modules
. But sinceds-test
andforge-std
do not have NPM modules, you still need to maintain a./lib
directory andremappings.txt
.The simplest fix would probably be to wrap these dependencies in NPM modules. This probably has use-cases outside just the one described above, but would help immensely for all the Hardhat folks that want to give Foundry a go.
Thanks! 🙏
Additional context
No response
The text was updated successfully, but these errors were encountered: