Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Metro bundler has encountered an internal error

See original GitHub issue

When I run yarn start in the terminal and use Expo App to open my RN Project in iPhone, an error appears as follows:

Issue Analytics

State:
Created 6 years ago
Reactions:5
Comments:49 (5 by maintainers)

Top GitHub Comments

61reactions

ghostcommented, Mar 2, 2018

easiest fix for me is killall node -9

26reactions

GentryRiggencommented, Jan 29, 2018

Fam, I fixed my issue and like most of them, it’s completely my fault. I was refactoring and deleted some files without cleaning up some imports of the deleted files. The only way I found this was to add a console.log in metro (node_modules/metro/src/lib/formatBundlingError.js).

function formatBundlingError(error) { console.log(error); }

Top Results From Across the Web

Metro Bundler has encountered an internal error, please ...

I`ve faced the same issue. In my case basically, it is because of some broken/wrong paths in imports statements. The issue gets solved...

metro bundler has encountered an error: while trying to ...

Building iOS bundle Metro Bundler has encountered an internal error, please check your terminal error output for more details Cannot read property 'status'...

metro bundler has encountered an internal error react native

When I received an offer for a software engineering role to build an app in React Native, I wasn't sure what to expect....

Javascript – Metro Bundler has encountered an internal error ...

after checkout when i say react-native run-android im getting below error. Metro Bundler has encountered an internal error, please check your terminal error...

Troubleshooting - React Native

The Metro bundler runs on port 8081. If another process is already using that port, you can either terminate that process, or change...