From 7cb431e78ec7f6e4daa8af015c2eac8f9fc557bd Mon Sep 17 00:00:00 2001 From: Rae Liu Date: Mon, 8 Jun 2020 19:03:33 -0700 Subject: [PATCH] We encounter regular resolution issue but was not captured by throwing proper resolution error, this handles the specific case we're seeing. --- .../metro/src/node-haste/DependencyGraph/ModuleResolution.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/metro/src/node-haste/DependencyGraph/ModuleResolution.js b/packages/metro/src/node-haste/DependencyGraph/ModuleResolution.js index 8a89e07120..9b6e5c13fa 100644 --- a/packages/metro/src/node-haste/DependencyGraph/ModuleResolution.js +++ b/packages/metro/src/node-haste/DependencyGraph/ModuleResolution.js @@ -316,7 +316,7 @@ class UnableToResolveError extends Error { try { file = fs.readFileSync(this.originModulePath, 'utf8'); } catch (error) { - if (error.code === 'ENOENT') { + if (error.code === 'ENOENT' || error.code === 'EISDIR') { // We're probably dealing with a virtualised file system where // `this.originModulePath` doesn't actually exist on disk. // We can't show a code frame, but there's no need to let this I/O