Migrate to new Spago #69
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
purescript-docs-searchdepends on spago to provide thespago docscommand in order to test itself. But the newest version of spago doesn't have that command yet, as its waiting onpurescript-docs-searchto update to the new spago.yaml format. This forms a kind of "chicken and egg" problem.The approach I am taking is to install both versions of spago. The legacy version is used for docs generation, but the new version is used to build & test.
After
spago docshas been ported to the new spago repo, we can come back and cleanup.Cleanup checklist:
npm exec --y --package=./node_module/spago-legacy --