For a long time I’ve been planning on using Next.js (or Nuxt if you fancy Vue more) over Meteor on this new project of mine because of two reasons:
- SSR (+ caching) for SEO and snappy page loads
- Dynamic imports for small bundles
Just so happens, Meteor has catched up and seems to support both. With
v1.7, Meteor is passing the competition with support for building two different bundles, one for modern browsers and one for the legacy ones, which is a huge win for bundle sizes beyond just code splitting.
So, has anybody toyed with the idea of “build your own Next.js” with Meteor? Is it doable? What is missing and what’s only half-way-there? What is Next.js doing better or what Meteor cannot do?
When I think about it, Meteor already has:
- It’s own node based server
- DDP + Methods or Apollo
- Dynamic imports / code splitting
- React for view layer
I’d be more than happy to do some extra leg work in the beginning to stay in the comfort of my familiar spaceship , but if the experience of building a Next.js -clone with Meteor is going to be more like a space trip with Laika the dog, then I’ll pass and just go with either Next.js or Nuxt which claim to provide what I’m looking for “out of the box”.
Any ideas or tips before I dive into Next.js docs?