Upgrade to webpack 2 in 1.0 branch #461
Comments
|
I'm planning on shipping 1.0 with this. It's only "fairly" stable atm though so don't want to convert over just yet. |
KyleAMathews
added
the
help wanted
|
Regarding this issue: #445 Maybe the migration to webpack 2 resolved the memory issue as well. |
|
Perhaps but I doubt it — it seems like that's a core design decision (which I agree with fwiw) so it's probably stayed. |
|
Hey there, has anyone picked up this ticket? If not, I can take it, I would love to contribute. |
|
@fitzk nope! Not yet! Feel free to take it on. Though you'll probably want to hit me up in Discord to chat about things as 1.0 is still a moving target. Thanks! |
|
For sure, thanks! |
|
There's a very helpful guide for this: https://webpack.js.org/guides/migrating/ |
|
Any progress on this? I'm finding it difficult to wrap my head around the stages (build-css, build-html, etc). Are they actively used? If not, perhaps just a standard dev / production config will work so that we can reap the benefits of webpack 2 |
|
@akadop not yet. It'll come though as part of the 1.0 release. The stages are a necessary part of how Gatsby works. We have to have at least two stages for building JavaScript bundles and HTML as they're very different way so using webpack. We added the CSS as an optimization so that we could easily inline CSS in the |
|
FYI webpack 3 is out for a while now :) (as I am writing 3.5.x) |
|
FYI, not having treeshaking with a newer webpack currently makes any site using gatsby with |
|
@LegNeato hoping to get Gatsby v2 with webpack 3 out in the next few weeks! @jquense has much of the work done already! Would love your help testing out alphas/betas. There's already alphas out and you can check out the work on the v2 branch. Closing this issue since we're not going to upgrade to webpack 3 for 1.x |
|
Hello ! Any news about the Webpack update progress? I'm stuck with some dependencies that need Webpack v2+ 😐 |
|
Still a bit off. @jquense has done a lot of the work but there's some other things I want to do for v2 that we're blocked on. I can't get to working on the upgrade for another couple weeks probably. My plan/hope is to have the release done by Christmas. |
|
FYI, for those who want dynamic import, just wait for gatsbyjs to upgrade webpack version. |
|
Any news on upgrading webpack? |
|
@felipearosemena It should come with Gatsby v2. |
|
See #4588 |
webpack 2 is fairly stable. Bundle sizes could reduce drastically via tree shaking.
The text was updated successfully, but these errors were encountered: