-
Notifications
You must be signed in to change notification settings - Fork 74
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
ParserError: Source "@chainlink/contracts/src/v0.8/interfaces/AggregatorV3Interface.sol" not found: File not found. Searched the following locations: "". #20
Comments
Hi @ujwanviera, I faced a similar issue and I ended up just using the same version as in the videos provided and that solved it. For example in your contract use
in you brownie-config/yaml file use 1.1.1
If you still facing an issue let me know |
But isn't a solution for DEC 2022.. |
Just use file path "@chainlink/contracts/src/v0.8/factories/interfaces/AggregatorV3Interface.sol" |
"#30 (comment)" |
Hey I just changed the remapping in foundry.toml and it seems to work remappings = [ |
I am taking @PatrickAlphaC tutorial but I am stack at one point. Brownie Fund Me course. I tried to compile it but it does not work.

here are my file (as the one provided by @PatrickAlphaC in the course repo).
Error:
brownie-config.yaml:

FundMe.sol (a part of it as I copied it from the course repo and made no modifications):
Any idea of why I am having this error? I have been browsing on google trying to figure it out but with no success.

In my attempts I created a setting.json file as in some posts some one suggested that it works with it but for me the error kept coming up
setting.json:
Thank you.
The text was updated successfully, but these errors were encountered: