-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Next + Native-Base error #39
Comments
Hey @gern132 I have in the same situation as you: trying to add Native Base to the stack My error is
Apparently, it was fixed on the version I have a feeling your error is not related to this repo Or it's related to your |
I ran
to bump I have an another error ./node_modules/react-native-web/dist/cjs/modules/useResponderEvents/ResponderTouchHistoryStore.js
TypeError: Property id of VariableDeclarator expected node to be of a type ["LVal"] but instead got "StringLiteral" |
I made some progress Nextjs builds! flexbox/react-native-universal-monorepo@d6f161f But I still have an issue with
|
I tried to use but I have more or less the same build issues |
After a month of exploring this configuration:
I am migrating to Nx https://github.com/flexbox/react-native-nx-monorepo because It will cover my needs in terms of CI. The NativeBase problem is related to the webpack config of Next.js and NativeBase. @gern132 |
Hello there! We are trying to use this monorepo to have a project with RN for mobile part and Next.js + NativeBase for the web. The issue that after we installed NativeBase in monorepo we got an errors and we think that the problem is lying somewhere in monorepo setup. BTW RN + NativeBase in monorepo works fine. To understand the issue we also tryed to run a new project (outside monorepo) with Next+NativeBase setup and thats works fine! Could you please give us a hint how to solve that issue, will be really appreciate for this
Error looks like:
This is our next config, with integrated config from NativeBase docs (https://docs.nativebase.io/install-next)
### INFORMATION
The text was updated successfully, but these errors were encountered: