Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

moduleraid breaks when used in a Webpack v5 bundle

See original GitHub issue

What the title says 😅 For some reaosn the result of require('moduleraid') in an app bundled with Webpack v5 is an empty object.

See a repro in this repo https://github.com/eramdam/moduleraid-webpack5-repro

Issue Analytics

State:
Created 3 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

eramdamcommented, Feb 25, 2021

@tomer8007 Hum, it seems like @pedroslopez’s fix allows moduleraid to inspect a webpack v5 bundle. My issue happens when bundling moduleraid in a webpack v5 bundle 😅

1reaction

eramdamcommented, Oct 22, 2020

@ScriptedAlchemy the issue isn’t that moduleraid can’t access Webpack v5’s package at runtime, which I would expect, but rather than using moduleraid in a Webpack 5 bundle results in the imported moduleraid code to not work/be an empty object 😅

EDIT: Weirdly enough, importing the source file directly into the codebase works fine, so I guess whatever is wrong lies in the dist file present in the npm package