-
-
Notifications
You must be signed in to change notification settings - Fork 777
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
Path dependencies module resolution bug #2278
Comments
Thank you |
Hi I would like to work on this issue. |
Thank you! Do you have an idea for how to approach this? |
Not sure yet, but I did reproduce the issue exactly as above and noticed that I could get /foo to build properly by deleting /foo/manifest.toml, waiting for a new manifest to be autogenerated, and running gleam build again. Looking inside /foo/manifest.toml, the difference i see is that simplifile was added to 'packages':
|
Description of behaviour
Given some project
foo
that has a path dependencybar
, ifbar
adds a dependencybaz
afterfoo
has already been built, attempting to rebuildfoo
will fail complaining that modulebaz
cannot be found.Steps to reproduce
The following steps but as a video
Given the following project setup:
If you then take the following commands:
And then update
bar/src/bar.gleam
like followingAnd then finally attempt to build foo again
~/foo $ gleam build
It will fail with the following error message:
The text was updated successfully, but these errors were encountered: