Terser Plugin – should it be an external?

[morozow]

Hi there,

Webpack Terser plugin kills mostly unrelated project webpack code source. I mean I use Terser plugin as a default configuration webpack part right in each project.

So that, why had this plugin been replaced to an external as I see.

Otherwise, that's a valuable application structure or that plugin must be the default for each part of a serverless maintenance.

Thanks.

[j0k3r]

I don't understand what you're asking.

There is no reference to Terser in the project. Also, we don't always use it in my company, even though we rely heavily on serverless-webpack.

[morozow]

Your project has an internal references for Terser. Nevertheless, have you compared an output size in bytes with the serverless approach? It appears I'm asking about an optimisation, rather than any way to be compiled.

[j0k3r]

I still don't get it.

Yes there is a reference to terser because serverless-webpack (obviously) request webpack which has terser-webpack-plugin as deps. There is nothing we can do about that.

[morozow]

@j0k3r Thanks for sharing. One suggestion – have you considered customising the Terser plugin configuration rather than using the default Webpack settings?
In my experience (especially in serverless environments like AWS Lambda), a tuned Terser setup – I mean, dropping console logs, enabling aggressive mangling, and disabling function name preservation – can significantly reduce the bundle size.
This in turn reduces (obviously) cold start latency, which can be critical for performance. If this repo is meant as a quick-start sample, that's fine. But if it's for production-ready setups, I'd definitely recommend evaluating a custom Terser config shared across projects.