Closed farnoy closed 9 years ago
Alright nevermind, specifying the main module in psc(...)
has fixed the issue.
Glat it works. I will take a look at that error message. It looks like the underlying error is being hidden. Thanks for the report.
In addition to looking at the error message, the example gulpfile should probably be changed to a valid one, since it causes this same error.
@porglezomp Good catch on the README. I've opened #42 for this.
Also, one final gotcha, it would be nice the module:
argument was more permissive and treated 'Main'
the same as ['Main']
. This probably won't matter much once the error messages are fixed though.
On the topic of the error message, while I was searching around and running into bug reports on other plugins, I found multiple references to exceptions not being caught by the plugin and bubbling up to a catchall somewhere inside gulp itself that produces the bad error message.
Let's get a fix in for the error messages first and see how that goes. If we need more flexibility in the type of the module argument we can look into adding that afterwards. And good to know about the catchall. I will do some digging on this.
Hi,
I'm setting up for purescript development and I've had gulp already, so I tried this:
I get
And if I remove the
pipe(gulp.dest(...))
call