-
Notifications
You must be signed in to change notification settings - Fork 117
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
Upgrade to webpack 5 #423
Comments
Hi @chrbala, while we consider this feature request, I recommend trying out our new |
I'd love to see support for webpack 5 as well. I believe gatsby v3 requires webpack 5. So using a different tool (esbuild) when using netlify + gatsby might not be ideal. Is there an existing work for making this project webpack 5 compatible? |
any updates on this? I see that PR is ready, why not to merge it? @erezrokah |
Hi all 👋 Very sorry for the delay on this. So it's not only about the code changes, more about their impact on existing users. We'll do it as a major version bump anyway, since it's a breaking change, but if there's anything we can do to make it easier for users to migrate or understand the breakage - it would be better to understand that in advance (and document it). One thing you can do to help is to try running with the suggested change (either by forking or by installing directly from the PR branch), and see the impact. |
Any update here? It's all very quiet. |
Is your feature request related to a problem? Please describe.
The most recent version of ts-loader does not work on Webpack 4.
Describe the solution you'd like
Upgrade to Webpack 5
Describe alternatives you've considered
Only use older versions of webpack plugins that work with Webpack 4.
Additional context
This is a breaking change, so it should be a major version upgrade to netlify-lambda.
The text was updated successfully, but these errors were encountered: