Add support for spago run with alternative backends

[tenniscp25]

Description of the change

• Made spago run call the backend with --run argument.
• Updated spago run specs for node backend.
• spago test still uses node backend.

As for the test, if creating a shell script and a batch file to echo $1 to check backend arg is the way to go, I'll be happy to implement it.

Checklist:

• Added the change to the "Unreleased" section of the changelog
• Added some example of the new feature to the README
• Added a test for the contribution (if applicable)

[f-f]

cc @csicar @andyarvanitis could you take a look at this and maybe try it out?

[csicar]

First of all, thank you for the contribution. It's awesome to see further work being done in that area.

This works properly with pskt. It does start the pskt --run, but I would be awesome if the --run options was passed the module to run. That way, we could also support spago test.

One problem, that remains is, that (at least pskt) does not know where it should look for the foreign files for the standard libraries. That problem is kinda orthogonal to this, but it means, that spago run does will fail for pskt while compiling the jar file, as the foreign files are not found.

[f-f]

Looks great, thanks! 👏

The only thing left is to update the fixture for the output when psa is installed (to reproduce locally just install purescript-psa and run the tests)

[tenniscp25]

Fixed.

[tenniscp25]

Oops.. wrong button 🙈

[f-f]

@tenniscp25 thank you for doing this! 🙂

[andyarvanitis]

Happy to try this, but it will have to be this weekend. Looking forward to it!

[andyarvanitis]

Runs fine with psgo; I tested both spago build and spago run. It looks like spago test behaves the same as spago run right now (I assume by design), which is fine as psgo doesn't have anything for test yet.