Upgrade to new spago

[CGenie]

This PR contains an upgrade of this package to the new spago with spago.yaml replacing spago.dhall, packages.dhall, bower.json.

[fsoikin]

Do the dependencies have to be explicitly versioned? I see the weren't versioned in the old spago config.

[CGenie]

No, they weren't, but I think it's a good practice to specify version numbers nevertheless.

In Haskell you have things like: https://hackage.haskell.org/package/cabal-constraints which pin the versions exactly.

If spec releases version 8.x.x, someone will soon discover that purescript-spec-discovery won't compile because of dependency errors and would try to fix it to work with newer version.

[fsoikin]

Isn't the whole point of package sets to avoid these things?

For example, if there is a new version of spec that makes discovery not build anymore, then discovery won't be included in the next package set. And anybody who needs it can just stay with the previous package set version, not upgrade to the new one.

[CGenie]

Yeah, maybe you're right, I'll fix these.

[CGenie]

Ah no sorry, I forgot that spago publish requires these things to be added. When I didn't specify the versions, it complained that it can't publish such a package.

[fsoikin]

Ok, good for now. I'll look into this some more later.

[fsoikin]

This can probably be omitted, right?

[fsoikin]

And this I guess?

[fsoikin]

@CGenie I think you need to update the GHA config too. See how GHA is failing?

[CGenie]

import fs15, { constants as fsConstants } from "node:fs/promises";
               ^^^^^^^^^
SyntaxError: The requested module 'node:fs/promises' does not provide an export named 'constants'

I guess we need nodejs at least 16, it's 14 in tests still. https://en.wikipedia.org/wiki/Node.js#Releases I guess version 22 is a safe bet now?

[fsoikin]

Still failing

[CGenie]

Yeah because I forgot about bower.

[CGenie]

I don't understand github. I wanted to set up my own runner for this but I don't know how.

[CGenie]

Thanks!