Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds support for using Rozenite for Web when mobile is served by Metro and the web app is served by Webpack Dev Server.
With this change, developers can keep Metro as the source of React Native DevTools data while serving the browser app from Webpack, and still have the browser show up as a debug target in React Native DevTools. The setup now covers both websocket and HTTP dev-middleware endpoints, so the web debugging flow works in split Metro + Webpack environments.
Documentation was also updated to describe the new setup and configuration path.
Context
Rozenite for Web previously assumed Metro was serving both mobile and web. That left a gap for projects where Metro is used for mobile development but Webpack Dev Server is used for the web app.
This change closes that gap by making the split setup a supported user flow. The goal is to let developers adopt Rozenite for Web in mixed-bundler projects without changing their existing dev-server responsibilities.
Reviewers should primarily evaluate whether the user-facing setup is clear and whether the documented Metro + Webpack flow matches expected Rozenite for Web behavior.
Testing
@rozenite/webpackage with test, typecheck, lint, and build runs.