Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
`worker: true` breaks parsing when minified production settings are used #114
Ran into another issue. If you'll recall my parse command:
Everything works fine until I go with
I tried using the papaparse.min.js to determine if it's grunt's uglify that is busting it but that seems to have no effect as the grunt task still concats and uglifies everything together. (I'm using the default gruntfile that the yeoman angular-fullstack-generator creates.)
After a bunch of tests I found that it works again when I comment out
I'll be leaving out the worker for the time being, but if you discover a fix that'd be great!
You're telling me... For development I've been using
I also see other issues with my codemirror text area, however, the input being passed to the parse is correct and the only difference between working and non-working parsing is
I'm going to try and comb through the processed JS to see if I can find anything helpful.
Also, thanks for the quick replies!
Okay, here's where I'm leaving it for today. I can see that I get to:
And based on the config earlier, when we receive a message we should hit
Node is just my server tech. The parse is being called from my angular
I've pinned it down to this block:
In the production build,
Below is the chain of logs I get. Maybe you can figure out what's not being called in the production version.