Next.js + Expo monorepo with blitz

[wyattades]

Greetings! The pivot to a framework-agnostic toolkit re-sparked my interest in blitz, purely for use of the zero-api queries/mutations feature (@blitzjs/rpc).

I managed to successfully* create a proof-of-concept monorepo containing a Next.js and Expo project that share all their UI code and data-fetching logic with [email protected]: https://github.com/wyattades/tely-app-demo

I wanted to create and share this project with the blitz team to help inform the development for non-next.js platforms. Here were some of the quirks I encountered:

• Expo uses the metro bundler instead of webpack, so I needed to port blitz's webpack loader (just for client, not server) to a babel plugin.
• Blitz uses Next.js useRouter, but the Next.js router context is not available in a native app, so I replaced next/router module with a no-op module.
• Blitz uses some web-only APIs that I had to polyfill: window.addEventListener, localStorage (@blitzjs/auth only? might be able to exclude this package from the native app)
• setting the API_BASEPATH in a native app is a bit awkward: process.env.__NEXT_ROUTER_BASEPATH = ..., but it could a blitz config value?
• tracking other issues here: https://github.com/wyattades/tely-app-demo/issues

I think some of these issues could be fixed by relaxing some usage of Next.js/web APIs (e.g. window.addEventListener?.(...), e.g. useRouter()?.isReady) or by continuing to separate Next.js/web code from the @blitzjs/rpc project.