Update for PureScript 0.15

[thomashoneyman]

Hi @nsaunders! We're using this package in the registry and are upgrading to PureScript 0.15 over there. This PR updates your library for compatibility with PureScript 0.15 packages, and I'll add it to the package sets once merged.

[thomashoneyman]

These dependencies were added because they are used in your source code but not explicitly listed as dependencies. Spago now throws an error if you do that, so I needed to install these.

Also, I've split your Spago file into a file for your library and other files for tests and examples. In the future the package sets will use the Spago file from your repository to determine your dependencies (rather than a separate list in the package-sets repo) so that helps you ship only the dependencies you need to.

[nsaunders]

Terrific news, thanks @thomashoneyman !

[nsaunders]

Thank you @thomashoneyman! I'm sorry I didn't get to this sooner, but I really appreciate you jumping in to take care of it.

[nsaunders]

Hmm, if you happen to notice this failure, don't sweat it... After reviewing spago.example.dhall, it's not obvious to me why the Effect.Console module wouldn't be available; so I'm sure it's just a (GitHub Actions-related) configuration issue on my part. I'll take a closer look later on today.

[thomashoneyman]

Ah, perhaps that needs to be spago -x spago.example.dhall run ... so it knows to include those dependencies (you don't use console anywhere in the main library).

[thomashoneyman]

Would you mind pinging me when a new version is published and I can add this to the package sets? Thanks!

[thomashoneyman]

@nsaunders Sorry to ping you again, but it looks like that fix to CI worked and this is now eligible for a new release. I'm only commenting because I know it's easy to forget (I forget to publish a new tag all the time!), but you may have other reasons to hold off tagging a new version.

[nsaunders]

Ah, perhaps that needs to be spago -x spago.example.dhall run ... so it knows to include those dependencies (you don't use console anywhere in the main library).

Good eye @thomashoneyman! I was looking at the wrong build step.

Would you mind pinging me when a new version is published and I can add this to the package sets? Thanks!

Certainly, I've tagged it as v3.0.0.

Sorry to ping you again, but it looks like that fix to CI worked and this is now eligible for a new release. I'm only commenting because I know it's easy to forget (I forget to publish a new tag all the time!), but you may have other reasons to hold off tagging a new version.

No worries! I'm sorry for the delay...

Thanks again for all your help!