-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Webpack error: require function is used in a way in which dependencies cannot be statically extracted #19
Comments
Webpack is a pain to work with lol, they provide a way to not process certain Let me see what can be donee here. |
Fixed in 1.1.2 |
Thanks for resolving that so quickly, although I think you may have published a local branch |
Also, we're seeing a different warning |
ohh ffs, you are right, I am refactoring other parts of the code and that file lingered there for some reason.... I'll just release the refactored version soon. The new warning is not showing up on my test project, could you elaborate on the repro steps? |
Cool, np
I'll setup a minimal case and share it with you some time over the weekend Thanks! |
Have raised #20 |
Hi, we're hitting an issue when webpack builds the output in CI mode auth0/auth0-spa-js#447
When we tested it originally we noticed a warning:
require function is used in a way in which dependencies cannot be statically extracted
but thought we could ignore it.But with the CI environment enabled, this turns into an error.
It seems webpack doesn't like the
var kRequire = require; kRequire('something');
happening in https://github.com/darionco/rollup-plugin-web-worker-loader/blob/master/src/helper/node/WorkerClass.js#L4The text was updated successfully, but these errors were encountered: