Skip to content

Failing resolving a module at runtime #15518

@indiketa

Description

@indiketa

Bug report

What is the current behavior?
Webpack compilation finishes without any error nor warning.
At runtime an error is thrown while importing a module through a dynamic import.

"User-space" code router.js:259:

pantalla = await import(
  /* webpackChunkName: "generales" */
  /* webpackMode: "lazy-once" */
  `pantallas/generales/${idPantalla}.js`);

The following error is thrown:

  router.js:368 TypeError: __webpack_require__.t is not a function
    at |chunkName: generales|groupOptions: {}|namespace object:20:1
    at async cargarPantalla (router.js:259:1)

This is the webpack-generated function causing the error:

function webpackAsyncContext(req) {
	return webpackAsyncContextResolve(req).then(id => {
		return __webpack_require__.t(id, fakeMap[id] | 16);
	});
}

t does not exist into __webpack_require__.
A needed function is deleted while compiling/optimizing or mangling is not working properly, i don't know.

What is the expected behavior?
The function should exist, this is an error into webpack module resolution code. No clues or workarounds.

Other relevant information:
webpack version: 5.70.0
Node.js version: 16.14
Operating System: Fedora 35
Additional tools: --

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions