I think "static site generator" is a more apt description than "webpack replacement". The React code in Gatsby is SSR'ed only (in production mode, anyways) maki

I think "static site generator" is a more apt description than "webpack replacement". The React code in Gatsby is SSR'ed only (in production mode, anyways) making writing idiomatic dynamic client-side React code very awkward. Also, Gatsby uses Webpack[1] and it doesn't expose compilation options in any meaningful way like webpack itself does (and it doesn't have a plug-and-play philosophy like Parcel either). I'm not a huge fan of webpack config API personally, but I certainly would never consider using Gatsby as an alternative generic purpose bundler! [1] https://github.com/gatsbyjs/gatsby/blob/561d33e2e491d3971cb2a404eec9705a5a493602/packages/gatsby/package.json#L135-L140 https://github.com/gatsbyjs/gatsby/blob/561d33e2e491d3971cb2...