Skip to content
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

Watch directory dependencies? #172

jmackie opened this issue Apr 9, 2019 · 2 comments


Copy link

commented Apr 9, 2019

Back at it again with the "workspace" problems...

If I have spago project A that depends on spago project B (in a sibling directory), it would be nice if spago build --watch run from project A responded to changes in project B. This may not be possible, but just a suggestion :)

See for a reproducible example of what I'd like to do (that link will probably rot, apologies)


This comment has been minimized.

Copy link

commented Apr 9, 2019

I think this would be quite fine to wire in, but I'll think a bit about the implications of this.

In the meanwhile you can solve this by:

  • not having B in the dependencies
  • ..but instead including its sources with the --path option. E.g. in our monorepo we use the following to build at the top level: spago build --path "packages/*/src/**/*.purs" --path "apps/*/src/**/*.purs"

(Btw if you'd like the link to not rot you could make a branch and link to it instead)


This comment has been minimized.

Copy link

commented Jul 10, 2019

@jmackie I opened #309 to fix this (and it will work correctly in all cases once #301 gets in too), could you try that branch and see if it works for you?

@f-f f-f self-assigned this Jul 10, 2019

@f-f f-f added the UX label Jul 10, 2019

@f-f f-f closed this in #309 Jul 17, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.