[redbar0n]

Someone asked on the other news item about onestack.dev :

> What is the added value of using it over just Expo?

My answer:

The added value of One is crossplatform compatibility with SSR, and HMR, all using Vite as the single bundler on all platforms.

Nate baked in his vxrn.dev project to get off of Metro and forked Expo Router to do that.

Since Expo Web has a large bundle size, requires NextJS for SSR, Solito for unified filesystem routing, and 2 bundlers: Metro as a bundler on RN plus a separate bundler like Webpack for web.

With One then all of that is integrated. With Zero as the optional data sync engine.

[darcien]

Metro is the default web bundler since Expo SDK 49[1] albeit missing vital features like bundle splitting. I think web bundle splitting is there in SDK 50? And the migration path from webpack to metro was pretty painful for big existing app.

So yes, the fact One use one single bundler from the start is nice win.

Also, looking at the direction Expo is taking, I believe they will eventually introduce SSR mode to Expo Router in the future.

[1]: https://blog.expo.dev/expo-sdk-49-c6d398cdf740

[mstade]

Great context, thank you for sharing!