Fabrizio Ferrai

I generally agree with @milesfrain that doing a `git clone` should be enough, but I think the main problem we have at hand is "discoverability", i.e. how would people know...

I'll close this since it looks like it's something that should be done outside of Spago, and [the discussion has moved to Discourse](https://discourse.purescript.org/t/featured-templates/1188)

Reopening this as we have a more pressing usecase now: a better test setup based on `spec-node`, as implemented in #1264. We should add `spec-node` to the default init template...

@fsoikin it's up for grabs so can be done whenever really 😄

There is already a draft PR that is addressing this: https://github.com/purescript/spago/pull/981

Ah right, CI fails because this change is correct 🙂 In the [`can't install (uncached) dependencies if offline` test](https://github.com/purescript/spago/blob/b491a799b5f192d485cc400dbe02dd3ac5ea9fda/test/Spago/Install.purs#L104) we were verifying that git repos never get cached, but with...

CI fails because on Windows (and only there) the folder in the cache is not found when we go copy it: ``` Error: ENOENT: no such file or directory, lstat...

Ah that's strange - I wonder if this is about Node versions? In CI we're using a pretty old one, 18: https://github.com/purescript/spago/blob/52999702842304b360b24f57571523564d261823/.github/workflows/build.yml#L41 Bumping it up to 22 might just fix...

Yes! You can swap the `Spec.it` of that test for `Spec.itOnly`

Trying this out on my windows machine, I can't reproduce it either unfortunately. I'd really like to merge this ASAP - but adding debug prints to CI seems to be...