psc-bundle is unable to parse module when `purescript-spec` is installed about purescript-spec HOT 6 CLOSED

Hmm, not able to recreate this. Could you provide a minimal project and list the commands you're running? Which versions of purescript-spec, psc and pulp are you using?

Thanks!

from purescript-spec.

Sure, here's output from my shell; let me know if you need any more info:

==> mkdir example

==> cd example

==> pulp -v
4.3.0

==> psc --version
0.7.0.0

==> pulp init
[installations elided]

==> pulp build --to out.js
* Building project in /Users/am/w/example2
* Build successful.
* Bundling Javascript...
* Bundled.

==> node out.js
Hello sailor!

==> rm -f out.js

==> pulp dep i purescript-spec
[installations elided]

==> pulp build --to out.js
* Building project in /Users/am/w/example2
* Build successful.
* Bundling Javascript...
The module could not be parsed.

* ERROR: Subcommand terminated with error code 1

==> psc-bundle output/**/*.js --module Main --main Main > out.js
The module could not be parsed.

==> rm -rf output/Test.Spec*

==> psc-bundle output/**/*.js --module Main --main Main > out.js

==> node out.js
Hello sailor!

from purescript-spec.

Thank you!

It seems that the escape sequence at https://github.com/owickstrom/purescript-spec/blob/12ee764274c0900c4f8167dd2ecb2b5f815a9280/src/Test/Spec/Console.purs#L22 gets interpreted during the PS -> JS compilation. The module in output/ contains the unescaped character which causes the bundle to fail. I'll try to move the string literal with the escape to a foreign function and see if that works.

Related issues: purescript/purescript#1265 and purescript/purescript#1266

from purescript-spec.

I did a workaround for this and released a new version 0.7.1. Please let me know if it works out.

Thanks for your feedback!

from purescript-spec.

The new version works - thank you!

from purescript-spec.

FYI purescript/purescript#1265 is fixed now!

from purescript-spec.