repack icon indicating copy to clipboard operation
repack copied to clipboard

How to locate cause of Error: ENOENT: no such file or directory

Open krzysztofzaluski opened this issue 1 year ago • 3 comments

I've noticed that if there is an error in the component code or some configuration file, such as missing a library in package.json and if I'm using it in the component or config file, then it always throws me an error when I try to bundle or run the app:

[Error: ENOENT: no such file or directory, open '/Users/krzysztofzaluski/Documents/react-native/Project/build/generated/android/index.bundle'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/Users/krzysztofzaluski/Documents/react-native/Project/build/generated/android/index.bundle'
}

so the problem is that the error message doesn't say anything specific that could help to locate the real issue, like the code line where the old removed import is still present, etc.

are there some ways how to track such a cases and locate such a files with issues?

krzysztofzaluski avatar Jun 25 '24 07:06 krzysztofzaluski