module: ignore resolution failures for inspect-brk

The resolution for the main entry point may fail when the resolution
requires a preloaded module to be executed first (for example when
adding new extensions to the resolution process). Silently skipping
such failures allow us to defer the resolution as long as needed
without having any adverse change (since the main entry point won't
resolve anyway if it really can't be resolved at all).

PR-URL: https://github.com/nodejs/node/pull/30336
Reviewed-By: Guy Bedford <guybedford@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>

2 files changed, 5 insertions, 0 deletions

diff --git a/test/fixtures/test-resolution-inspect-brk-main.ext b/test/fixtures/test-resolution-inspect-brk-main.ext
new file mode 100644
index 0000000000..e69de29bb2
--- /dev/null
+++ b/test/fixtures/test-resolution-inspect-brk-main.ext
diff --git a/test/fixtures/test-resolution-inspect-brk-resolver.js b/test/fixtures/test-resolution-inspect-brk-resolver.js
new file mode 100644
index 0000000000..fdfb5ca5b1
--- /dev/null
+++ b/test/fixtures/test-resolution-inspect-brk-resolver.js
@@ -0,0 +1,5 @@
+'use strict';
+// eslint-disable-next-line no-unused-vars
+const common = require('../common');
+
+require.extensions['.ext'] = require.extensions['.js'];