NodeJs API + Webpack 2 Production Builds = Error: Received packet in the wrong sequence

[jgrauel]

Hey - I love this module, thanks. I would love to use it in a nodeJs Api we are building, however I am running into an {odd?} issue where I am unable to move my code into a production environment. Every time I compile with webpack without setting devtool="eval" causes any attempt to make a connection result in an Error: Received packet in the wrong sequence.
My understanding is the devtool option controls if and how Source maps are generated from the compile process. I am not sure why exactly this would effect the execution of code, no errors result from actual compiling. Would love to know if there is some setting I am missing or way to get this working. Thanks

[dougwilson]

There is a precious issue still open about this, but I'm not sure what the fix is. If you can PR a fix, I'll be happy to merge it.

[dougwilson]

• previous issue

[jgrauel]

I saw the previous issue but it mentioned the additional use of Electron? and i wanted to specifiy it was just webPack and the module straight way

[jgrauel]

I am honestly unclear where to begin to fix , so would welcome guidance :)

[dougwilson]

I haven't used webpack, and really have no idea why it would be broken when using it...

[sidorares]

@jgrauel what's the reason you need webpack in the first place?

[jgrauel]

First I started using it so I can write in ES6 and its nice to have the files packed up on the server. So I found out that the error only occurs IF the webpack.optimize.UglifyJsPlugin is used. So that is progress, you can package/minimize without the Uglify. And that gives us a point of where to look. I am looking up if it has to do with specific settings only

[jgrauel]

Let me clarify, I know you can write in ES6 without web pack, but it allowed for the transition to be a bit smoother....

[jgrauel]

I use it to compile the code for client side as well :)

[jgrauel]

From what I have learned so far, as long as you set the option of mangle:false, the uglify plugin will not cause the error in the code. This is using webpack 2.2

[thewillhuang]

do something like https://github.com/apex/apex/blob/master/_examples/babel-webpack2/webpack.config.babel.js I don't recommend mangling anything as that would change variable names in unexpected places.

[dtslvr]

@jgrauel Have you found a way to also use mangle: true in the meantime?

[wenisy]

@jgrauel @dtslvr
Same question as above, do you find a way to solve it with mangle: true ?