webpack 5 dynamic require syntax causes un-necessary files to be traced/included for lambdas

[ijjk]

What version of Next.js are you using?

10.0.5 (canary as well)

What version of Node.js are you using?

v12.20.0

What browser are you using?

all

What operating system are you using?

macOS, Linux, Windows

How are you deploying your application?

Vercel

Describe the Bug

When dynamic imports are used dynamic chunks are created for the server build and dynamic required.

In webpack 4 the syntax used to require these dynamic chunks was able to be statically evaluated:

/******/ 		if(installedChunks[chunkId] !== 0) {
/******/ 			var chunk = require("../" + ({}[chunkId]||chunkId) + "." + {"0":"432e819ee916cf1fe474","1":"c1993a54b4b250bfacf9","2":"cfea81a5890bf53bdfc6","3":"944259e4b104c150480c"}[chunkId] + ".js");

In webpack 5 the syntax used is no longer able to statically evaluated which requires dependency tracing solutions to guess which files are needed in the relative directory used usually causing entire directories that aren't needed to be marked as needed e.g. the entire .next/serverless/pages directory is being included from the below require.

	// "1" is the signal for "already loaded"
/******/ 			if(!installedChunks[chunkId]) {
/******/ 				if(true) { // all chunks have JS
/******/ 					installChunk(require("../../" + __webpack_require__.u(chunkId)));
/******/ 				} else installedChunks[chunkId] = 1;
/******/ 			}

Expected Behavior

To be able to trace and include only the needed files in webpack 5 the same way we were able to in webpack 4

To Reproduce

Use webpack 5 with a dependency tracing solution like node-file-trace to detect needed files

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.