Upgrade to webpack 5

[chrbala]

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.

[erezrokah]

Hi @chrbala, while we consider this feature request, I recommend trying out our new esbuild based bundler:
https://www.netlify.com/blog/2021/04/02/modern-faster-netlify-functions/
as it supports TypeScript and new ECMAScript features out of the box (I'm assuming that's the reason you're using netlify-lambda).

[bpinto]

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?

[SupersonicMagpie]

any updates on this? I see that PR is ready, why not to merge it? @erezrokah

[erezrokah]

Hi all 👋 Very sorry for the delay on this.
Since moving to Webpack 5 removes some functionally (the merge.smart logic), we'll need to do some manual testing on the PR to see the impact. I haven't been able to do it (yet).

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.
That would help us understand the impact on existing users.

[arsinclair]

Any update here? It's all very quiet.