-
Notifications
You must be signed in to change notification settings - Fork 3
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
Does not support importing external libraries when using workspaces (like in yarn and lerna) #17
Comments
Hi @alesanro , Thanks for raising this. Can you please add steps to reproduce it? That will be really helpful |
@alesanro I got your point. Actually contract with import is flattened using the package sol-straightener. To determine the path of node_modules folder, it uses default way suggested by npm using npm root. Although it should work properly in this case too but I am not sure how we can incorporate the required changes. |
@Aniket-Engg Hi, I've made MR for |
That's great. I will review and merge it. |
In case of having several workspaces with packages and smart contracts imported libraries are searched only inside this package node_modules but probably should also have a shot on looking for upper-level node_modules like npm/yarn module resolution do.
The text was updated successfully, but these errors were encountered: