Closed brodycj closed 5 years ago
That should just be a warning tho, right? (not ideal for sure but trying to understand)
So I published 0.8 which bumps react-native-web to 0.11 and use react-360 instead of react-vr
That should just be a warning tho, right?
I get a build error on react-native-web-starter
, also if I would use Razzle web server. The build error is reproduced by the project I posted on GitHub. The web page shows a build error in case of both react-native-web-starter
and the Razzle web server.
UPDATED: I see no warning or error with version 0.8.0 (my bad).
I get a build error on react-native-web-starter, also if I would use Razzle web server
I'd say that's an issue with your configuration. Webpack only shows a warning as it should.
My bad, looks like you did solve it in 0367d9856488cbcb2939776590c9127dabb5d3e2. I will test it and confirm.
Thanks @mathieudutour for the quick updates, version 0.8.0 works for me like a charm on both brodybits/react-native-web-starter
and Razzle web server. No warning message, no error message with RNW 0.11.2.
Description
If I would try version
0.7.1
withreact-native-web
version0.11.2
in https://github.com/brodybits/react-native-web-starter/tree/demo-with-react-primitives-build-issue, then I continue to experience the build issue reported in #129. Here is the output from the failed build:My reproduction is based on a "Frankenstein" starter app by @joefazz. I suspect it should be possible to apply a workaround in the build, would personally favor a cleaner solution.
Workarounds
This issue would disappear if I would try the following:
react-native-web
version0.10.1
How to reproduce
git clone https://github.com/brodybits/react-native-web-starter
git checkout demo-with-react-primitives-build-issue
in the git cloneyarn
to installyarn web
, which will attempt to build and run on the browserA possible solution
react-native-web
>= 0.11.0 inpeerDependencies