You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
» spago run --backend-args '--help'
Reading Spago workspace configuration...
✓ Selecting package to build: html2halogen
Cloning https://github.com/purescript-web/purescript-web-dom.git
✘ Could not read config at .spago/p/web-dom/master
Error:
Did not find `.spago/p/web-dom/master/spago.yaml`.
By the way, perhaps the error message can be improved a bit as well. As far as i understood the config must always be called "spago.yaml" so "could not read" and "did not find" seem a bit double. What about Could not find the spago.yaml config file in web-dom?
The text was updated successfully, but these errors were encountered:
If the upstream library that you are adding has a spago.yaml file, then Spago will just pick up the dependencies from there. If that's not the case, then you'll have the provide the dependencies yourself, adding a dependencies field.
ok got it. Why close the issue though? In this case there is a good workaround to which the error message could point. Is that not a todo worth of the issue being open?
I vaguely remember this might have been discussed somewhere before. But i'm not sure if it does have it's own ticket.
I like to use this package https://pursuit.purescript.org/packages/purescript-web-dom/6.0.0/docs/Web.DOM
But than the latest version because of this commit purescript-web/purescript-web-dom#59
I specify it like this
This is my console output
By the way, perhaps the error message can be improved a bit as well. As far as i understood the config must always be called "spago.yaml" so "could not read" and "did not find" seem a bit double. What about
Could not find the spago.yaml config file in web-dom
?The text was updated successfully, but these errors were encountered: