-
Notifications
You must be signed in to change notification settings - Fork 26.2k
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
with-react-native-web React 18 #41010
Comments
Hi, the example should continue working, even if you upgrade to React 18. I upgraded the dependencies. 👍 |
…#41024) Closes vercel#41010 ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
I understand that the example still works, my question was regarding how would a refactor be made as to
Right now the example takes advantage of this method but in the documentation it discourages the usage of this method with React 18. How would the same behavior be achieved without using getInitialProps and renderPage in React 18 is my question. Thanks for the swift reply and I apologize for marking this as bug which is probably not the right way to raise this issue. Have a nice day. |
@AndreasBBS Did you figure it out? |
Not really. I'm hoping this upcoming even the next team has coming in October might give me more insights. |
I already figured it out. RNfW 0.18 does not enable React 18 features yet, but it's already in https://github.com/necolas/react-native-web/commits/0.19-dev. So I believe the example is OK. |
…#41024) Closes vercel#41010 ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Verify canary release
Provide environment information
Which example does this report relate to?
with-react-native-web
What browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
next start
Describe the Bug
There's not really a bug this is more a question for the future relating to React 18.
In your documentation for the custom document there's a note saying
How would this example look in a React 18 scenario?
Is this one of the cases where it's not possible to avoid customizing through getInitialProps and renderPage?
Expected Behavior
I would expect to be able to run this example using React 18 without leveraging getInitialProps and renderPage in_document.js
To Reproduce
Does not apply
The text was updated successfully, but these errors were encountered: