fix(webpack): externalize server source-map to prevent RangeError

For some reason we see intermittent failures with the source-map-support package (examples: evanw/node-source-map-support#252 and evanw/node-source-map-support#93). The fix that worked for us seems to be to externalize the source-map. Co-authored-by: Markus Wolf <[email protected]>
xing · Jan 12, 2022 · 0df73c9 · 0df73c9
1 parent f8b6194
commit 0df73c9
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/packages/webpack/lib/configs/node.js b/packages/webpack/lib/configs/node.js
@@ -169,7 +169,7 @@ module.exports = function getConfig(config, name, buildDependencies) {
       maxEntrypointSize: 52428800,
       maxAssetSize: 52428800,
     },
-    devtool: 'inline-source-map',
+    devtool: 'source-map',
     watchOptions: { aggregateTimeout: 300, ignored: /node_modules/ },
   };
 };
diff --git a/packages/webpack/lib/utils/compiler.js b/packages/webpack/lib/utils/compiler.js
@@ -21,7 +21,7 @@ function startCompilation(webpackConfig, options = {}) {
   const compiler = createCompiler(webpackConfig);
   const output = join(webpackConfig.output.path, webpackConfig.output.filename);
 
-  sourceMapSupport.install({ environment: 'node', hookRequire: true });
+  sourceMapSupport.install({ environment: 'node' });
 
   return new Observable((subscriber) => {
     const callback = (error, stats) => {