Can't resize interface while webpack is doing synchronous work about webpack-dashboard HOT 7 CLOSED

This should do it, eh? #50

from webpack-dashboard.

how would you go about doing that? in general?

from webpack-dashboard.

Spawn a subprocess with webpack in and use a socket to communicate

This package wraps all this for you in a postMessage API:
https://www.npmjs.com/package/webworker-threads

On 16 Aug 2016 00:08, "Ken Wheeler" [email protected] wrote:

how would you go about doing that? in general?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#30 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZQTHWZfwt-M8r_EvQ7ivsI8thlSlITks5qgPFUgaJpZM4Jk268
.

from webpack-dashboard.

That sounds pretty cool, I'll check that out

from webpack-dashboard.

@graingert I got started, but it looks like because i'm using express, that spawns a new process for dev server, so I lose process.send.

https://github.com/FormidableLabs/webpack-dashboard/tree/separate-processes

How does a unix socket work? I feel like if I run webpack-dev-server -- nodemon index.js, thats like 3 processes down, and process.env stuff won't get picked up. What's a more global option?

from webpack-dashboard.

Yeah so you create a temporary directory and choose a path inside that
directory and pass it to
https://nodejs.org/api/net.html#net_server_listen_path_backlog_callback you
could also use a TCP socket with a random port.

You just need to connect to the same socket in your plugin by passing the
socket connection details in an environment variable or something

On 16 Aug 2016 23:41, "Ken Wheeler" [email protected] wrote:

@graingert https://github.com/graingert I got started, but it looks like
because i'm using express, that spawns a new process for dev server, so I
lose process.send.

https://github.com/FormidableLabs/webpack-dashboard/tree/separate-processes

How does a unix socket work? I feel like if I run webpack-dev-server --
nodemon index.js, thats like 3 processes down, and process.env stuff won't
get picked up. What's a more global option?

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
#30 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZQTCkj9bv87xMTYkDn7XcjCK7JHxGGks5qgjyLgaJpZM4Jk268
.

from webpack-dashboard.

Think this can be closed but want to confirm /cc @kenwheeler @graingert

from webpack-dashboard.