I'd be very interested in seeing a prototype of Gatsby using Parcel — it definitely seems like it'd provide big speedups.
It wouldn't be possible to try the port until we finish the webpack 3 upgrade as Gatsby core uses require.ensure
still for code splitting. Once we're using async import, it'd be much easier to try the port.
Parcel fits in very well with Gatsby design philosophy @kylemathews
Would it be faster if gatsby is using Parcel?
This would be awesome.
i dont know how much is needed to "prototype" gatsby but i did a parcel SSG recently: https://github.com/sw-yx/boring-ssg
parcel lacks the event system to truly parallelize builds, and I raised an issue here: https://github.com/parcel-bundler/parcel/issues/1660
once that gets built in, parcel-based SSGs should easily outperform webpack-based ones.
I would love to see this!
BUMP!
Hiya!
This issue has gone quiet. Spooky quiet. 👻
We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
Thanks for being a part of the Gatsby community! 💪💜
Adding the request
@KyleAMathews - Hey! It it looks like parcel supports code-splitting with the current version:
https://parceljs.org/code_splitting.html. I like that parcel is all about trying to minimize configuration
Hi there, I think a lot of work is required in order to migrate. I think the webpack ecosystem is huge, tried and tested by the industry.
I am closing this issue, but feel free to reopen.
Happ Hacking :+1:
Most helpful comment
I'd be very interested in seeing a prototype of Gatsby using Parcel — it definitely seems like it'd provide big speedups.
It wouldn't be possible to try the port until we finish the webpack 3 upgrade as Gatsby core uses
require.ensure
still for code splitting. Once we're using async import, it'd be much easier to try the port.