Closed liebharc closed 1 year ago
Hi @liebharc! Thanks for the issue report. However, I'm having trouble reproducing your error. When I run these command on a clean repo, I get:
$ pnpm install
$ cd apps/web
$ pnpm dev
Which makes sense. This repository does not have any opinion on how packages are being built. Just to keep the example as "vanilla" as possible, see my comment for more info.
When running these commands, I don't have any issues whatsoever: (just on Windows 11, without WSL)
$ pnpm install
$ pnpm build
$ cd apps/web
$ pnpm dev
It might be interesting to debug the Next config and check if the react-native-web
integration is working as expected. Unfortunately, I can't do that on my end since I can't repro it.
The integration itself comes from Vercel's React Native Web starter: https://github.com/vercel/turbo/blob/main/examples/with-react-native-web/apps/web/next.config.js
Success :). I've updated pnpm to 7.23.0 and repeated your steps (including the build step) and this way the Next.js app starts without issues. Thanks for your help!
No problem, glad you solved it! Also, small heads up, I just made a change that supports the "decoupled build system", while keeping live reload alive :) (see PR #78)
Nice 😊
Description of the bug
I hope I haven't just overlooked something obvious, but the web app throws an error directly at startup:
I see that there is a resolve alias in the next.config.js, but it doesn't seem to kick in?:
To Reproduce
What steps did you perform which led to this issue?
Expected behavior
Showing the page with "Hello from ..." as the mobile app does.
Actual behavior
Throws a "Module not found" error. Full next.js log:
Additional context
Environment: Tried it on Windows directly and inside the Linux Subsystem (WSL).
On the Debian WSL these are the versions installed: