You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the event of a failed compilation Webpacker::Compiler#run_webpack will swallow the output of stdout and only show the output of stderr.
If webpack is incorrectly outputting on StdOut, as seems to be the case with a missing node module, then the user just see's a blank error with no further information
Compilation failed:
Happy to submit a patch to resolve this - not sure on the best approach? Options I can think of are
I can confirm that this indeed occurs frequently (the last case was when I by accident declared already declared const) as well as that solutions proposed by @jebw do indeed fix it.
I'm also happy to submit patch, but don't want to steal @jebw's credit.
I suggest this to be treated as a high priority bug, because it makes webpacker pretty much useless.
In the event of a failed compilation
Webpacker::Compiler#run_webpack
will swallow the output of stdout and only show the output of stderr.If webpack is incorrectly outputting on StdOut, as seems to be the case with a missing node module, then the user just see's a blank error with no further information
Happy to submit a patch to resolve this - not sure on the best approach? Options I can think of are
Thanks
The text was updated successfully, but these errors were encountered: