Update to PureScript v0.15.0

[JordanMartinez]

Description of the change

Backlinking to purescript/purescript#4244

Migrates FFI to ES modules

---

Checklist:

• Added the change to the changelog's "Unreleased" section with a reference to this PR (e.g. "- Made a change (#0000)")
• Linked any existing issues or proposals that this pull request should close
• Updated or added relevant documentation
• Added a test for the contribution (if applicable)

[JordanMartinez]

🏓 @thomashoneyman CI will fail due to using spago to bundle things. Since this isn't exactly a commonly-used lib, how do you want to proceed?

[thomashoneyman]

My initial thought is to use esbuild directly to bundle, as will be done under the hood with Spago in the future. Does that seem like an appropriate plan? Perhaps @sigma-andex knows the correct way to do this?

Otherwise, we could comment out the tests, create an issue to come back to it, and move on.

Either way we need to add aff-promise to the prepare-0.15 package set.

[JordanMartinez]

Either way we need to add aff-promise to the prepare-0.15 package set.

Ah, good point.

[JordanMartinez]

My initial thought is to use esbuild directly to bundle, as will be done under the hood with Spago in the future. Does that seem like an appropriate plan? Perhaps @sigma-andex knows the correct way to do this?

That can work. Maybe do that for now and then use spago bundle, which will use esbuild under the hood, later?

[sigma-andex]

This is running on node, right? If so we don't even need to bundle

[sigma-andex]

If you want to bundle, this can be used:

[debug] Running command: `echo "import { main } from './output/Main/index.js'
main()" | /usr/local/bin/esbuild --platform=node --format=esm --bundle  --outfile=index.js`

[JordanMartinez]

This is running on node, right? If so we don't even need to bundle

Thanks for the tip!