Replies: 1 comment 1 reply
-
Alright... I've solved the issue. The problem was that I was referencing in my collection some variables that were not available any more. No idea why this didn't throw a simple reference error pointing at the collection. Furthermore I'm configuring Webpack this way now: webpack: (config) => ({
...config, resolve: {
...config.resolve, fallback: {
...config.resolve.fallback,
fs: false,
}
}
}) I don't know if this is better than the way I did before. But it works. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm gettting these errors from Webpack:
After some research I started using these config lines for Webpack in order to reference an empty mock-object instead of the module.
I must admit that I don't really understand why I'm doing this. But it worked for me.
Since today I get the following errors:
Now however it doesn't work to use mock paths for these modules.
What do I have to do? How and where do I need to install the required polyfills?
Thanks for any support.
Beta Was this translation helpful? Give feedback.
All reactions