You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because a single major version of this loader supports three different major versions of webpack, but assumes that "require" will find the right one, it will find the wrong one if the project level and a dependency of the project depend on different versions of webpack as described in that issue.
... A better resolution is proposed, but requires implementation here now that webpack has done their bit starting in webpack 5 to make it possible to find what you need without using "require".
html-webpack-plugin used to have a similar issue, but in their new major release they only list webpack 5 as a compatible peer dependency. That strategy also solves the issue.
The text was updated successfully, but these errors were encountered:
Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).
I hope to see your helper-created issue very soon!
Please see:
webpack/webpack#12606
Because a single major version of this loader supports three different major versions of webpack, but assumes that "require" will find the right one, it will find the wrong one if the project level and a dependency of the project depend on different versions of webpack as described in that issue.
In this comment:
webpack/webpack#12606 (comment)
(And some of the related comments)
... A better resolution is proposed, but requires implementation here now that webpack has done their bit starting in webpack 5 to make it possible to find what you need without using "require".
html-webpack-plugin used to have a similar issue, but in their new major release they only list webpack 5 as a compatible peer dependency. That strategy also solves the issue.
The text was updated successfully, but these errors were encountered: