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
Hey there 👋 Just wanted to give you a heads up that there are two changes in the pipe upstream, aimed at making integration better for webpack. I'm planning on sending a PR mkaing use of the changes, but thought it'd be neighborly to give you a heads up.
In particular the output change means, as is, the plugin won't write anything out now, since the changes go through the reporter. Hopefully this is a good thing tho since we can actually pipe those messages into webpack directly and let folks using webpack output plugins handle them.
The filesystem PR should give the opportunity to use webpacks fs wrapper which is heavily cached, should cut down on IO from disk and give a small speed improvement (hopefully)
The text was updated successfully, but these errors were encountered:
Hey there 👋 Just wanted to give you a heads up that there are two changes in the pipe upstream, aimed at making integration better for webpack. I'm planning on sending a PR mkaing use of the changes, but thought it'd be neighborly to give you a heads up.
In particular the output change means, as is, the plugin won't write anything out now, since the changes go through the reporter. Hopefully this is a good thing tho since we can actually pipe those messages into webpack directly and let folks using webpack output plugins handle them.
The filesystem PR should give the opportunity to use webpacks fs wrapper which is heavily cached, should cut down on IO from disk and give a small speed improvement (hopefully)
The text was updated successfully, but these errors were encountered: