-
Notifications
You must be signed in to change notification settings - Fork 28
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 5 support #103
Comments
First step is to add webpack 5 to the test suite here: Lines 16 to 18 in 233db82
Lines 15 to 17 in 233db82
However, it sounds as though you're simply providing the options to rails-erb-loader is an old way that is not longer valid:
Additionally it sounds like the API for reading options may have changed:
Note that in making required changes (if any) we will also need to continue to support older versions of webpack. Additionally for this change to be complete we will need to update the README to show the current recommended way to configure webpack 5.
I myself will not be making this change, but will happily accept a PR that does so, provided the above is included, or explanation is given as to why it was not required. |
Webpacker 6 has already included a default rule for |
@PikachuEXE Ah this is correct, and yes it 'just works' in webpacker 6 without any user config at all - thank you very much. |
Reopening until we can confirm compatibility with webpack 5. |
Hi there, So i'm testing out Webpacker 6 which uses webpack 5 - I'm having trouble initializing the loader.
Which gives me this error
Any ideas how to adapt the loader? Do you need to do work to support the new webpack 5 plugin API?
The text was updated successfully, but these errors were encountered: