wwwwwwwwwwwwwwwwwww

FAQ

Is this production ready?

All features for 1.0 now work and half are well tested. We've been using it for tamagui.dev for 6 months or so. Native we'd like to think is stable summer 2025.

What's breaking?

There's a few things that we need to improve:

  • Hot reloading easily breaks.
  • Package compatibility - you'll likey need to use the deps options as we fix issues.

See the Status documentation for more on the general stability of the high level API surfaces.

How does it compare to Expo Router / Metro?

One started as vxrn, a library we made that let Vite serve React Native. To test if it worked well, we ported Expo Router and generally got it working. We didn't implement DOM components and a couple other features, but we did add things like render modes, loaders, middlewares, and other things.

We added a CLI that serves and builds web, iOS and Android, and all the web features build to a production Hono server.

Why Vite?

It feels light and simple, runs fast and is easy to customize. It has many web features that are all done well, relative to other bundlers, and the Vite types, documentation, type-documentation, RFC process, and commitment to community are all "god-tier".

Will you support RSC?

We benefit from a lot of complexity focus on server-rendering without RSC, and with a smart data library you can get many of the same features with better end-user performance and simpler code.

We're open to a limited form of RSC that keeps things simple.

What's the npm package?

It's one, thanks to Dan Maier.

Edit this page on GitHub.