-
-
Notifications
You must be signed in to change notification settings - Fork 489
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
Bug, or clarification needed around forge install
, and the lib folder
#275
Comments
positonic
changed the title
Clarification around
Bug, or clarification needed around Apr 21, 2024
forge install
, and the lib folderforge install
, and the lib folder
This project is not meant to be used with Forge. It's a front-end development environment. For smart contract development, check out my Foundry template: |
Also, I recommend against using git submodules: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using forge with create-eth, and when I run forge install it installs in the lib folder in the root of my project.
I appear to be having an issue with paths though. My packages/foundry/remappings.txt file has the line:
oz-upgradeable=/lib/hypercerts/contracts/contracts/lib/openzeppelin-contracts-upgradeable/contracts/
It's throwing an error:
Which basically shows that it's looking for the lib folder relative to the foundry folder:
packages/foundry
I'm stuck on how to get around this.
I've tried:
yarn test --lib-paths ./lib
The only way I have been been able to get it working is to hard code the path to the folder like this:
oz-upgradeable=/Users/me/code/hyperstaker-mono/lib/hypercerts/contracts/lib/openzeppelin-contracts-upgradeable/contracts/
This is problematic as it's a shared repo which others work on, and I'm a bit confused by this behaviour altogether, and wonder if I'm doing something wrong, or if it's a bug?
The text was updated successfully, but these errors were encountered: