Rerunning Metro: Another process is running on port 8081. ? Use port 8082 instead?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.6k
- Forks
- 696
- Avg merge
- 8m
- Merged PRs (30d)
- 7
Description
Hallo, using,
"react": "19.1.4",
"react-native": "0.81.6",
Since upgrading to the new Architecture , Metro has changed and it doesn't have the option to press A and rebuild the project again, so I used to just rerun again the process for the new Arch , but after some updates it stopped working and it says another processes is running at that port but its the same metro with the same project, does anyone have a clue? its abit annoying to try to kill it and rerun it again :p
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reproducing the port-8081 conflict with React 19.1.4 and React Native 0.81.6 after enabling the New Architecture, then trace Metro's handling of an existing process; done means rerunning the same project no longer requires manually killing and restarting Metro.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100