-
-
Notifications
You must be signed in to change notification settings - Fork 386
filename and chunkFilename functions #417
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
Comments
Sorry without reproducible test repo we can't help |
@aaarichter
|
Same issue. My configuration is vanilla:
But I get the following error:
I tried multiple configurations without any success. For the moment, I reverted to version 0.6.0. |
node_modules/mini-css-extract-plugin/dist/index.js:183 result.push({
filenameTemplate: ({
chunk: chunkData
}) => this.options.moduleFilename(chunkData),
...
}); to this result.push({
filenameTemplate: "asdfasdf",
...
}); cleared buildtime error (and breaked build of course). |
Keep katex at 0.10.x, mini-css-extract-plugin at 0.6.x (webpack-contrib/mini-css-extract-plugin#417), and typescript-eslint at 1.x for now. Upgrade everything else. Signed-off-by: Anders Kaseorg <[email protected]>
Keep katex at 0.10.x, mini-css-extract-plugin at 0.6.x (webpack-contrib/mini-css-extract-plugin#417), and typescript-eslint at 1.x for now. Upgrade everything else. Signed-off-by: Anders Kaseorg <[email protected]>
Keep katex at 0.10.x, mini-css-extract-plugin at 0.6.x (webpack-contrib/mini-css-extract-plugin#417), and typescript-eslint at 1.x for now. Upgrade everything else. Signed-off-by: Anders Kaseorg <[email protected]>
Keep katex at 0.10.x, mini-css-extract-plugin at 0.6.x (webpack-contrib/mini-css-extract-plugin#417), and typescript-eslint at 1.x for now. Upgrade everything else. Signed-off-by: Anders Kaseorg <[email protected]>
Keep katex at 0.10.x, mini-css-extract-plugin at 0.6.x (webpack-contrib/mini-css-extract-plugin#417), and typescript-eslint at 1.x for now. Upgrade everything else. Signed-off-by: Anders Kaseorg <[email protected]>
Keep katex at 0.10.x, mini-css-extract-plugin at 0.6.x (webpack-contrib/mini-css-extract-plugin#417), and typescript-eslint at 1.x for now. Upgrade everything else. Signed-off-by: Anders Kaseorg <[email protected]>
Keep katex at 0.10.x, mini-css-extract-plugin at 0.6.x (webpack-contrib/mini-css-extract-plugin#417), and typescript-eslint at 1.x for now. Upgrade everything else. Signed-off-by: Anders Kaseorg <[email protected]>
I am still having this issue.
|
Keep katex at 0.10.x, mini-css-extract-plugin at 0.6.x (webpack-contrib/mini-css-extract-plugin#417), and typescript-eslint at 1.x for now. Upgrade everything else. Signed-off-by: Anders Kaseorg <[email protected]>
same issue here. any updates? |
Close in favor #67 |
Uh oh!
There was an error while loading. Please reload this page.
So I have been upgrading from version 0.2.0 step by step until 0.7.0. I noticed that in between the minor versions the
filename
andchunkname
functionality changed or broke when replacement functions are used. Updating to the latest I see errors likeExpected Behavior
No error and stable behavior of those replacer. (tbh I froze the version due to buggy behavior in between minor versions)
On such errors the call stack should be outputted too.
Actual Behavior
Errors are shown.
Code
How Do We Reproduce?
No idea, I just upgraded and got the error when running webpack
The text was updated successfully, but these errors were encountered: