By your same logic, there’s no point in not minifying the files. It is really fast (if we minify before merge); it doesn’t ruin the debugging process (we’re all using source maps anyway, right?); and if indeed the minified code is the same as the original code, why output unminified code at all?

Here’s another way of looking at it. Webpack/Gulp/Browserify developers and users write extra code to not minify in dev mode. My argument: that extra code creates zero value, in theory.

(I know that some steps, like tree-shaking, should come at the end of the pipeline and might take time. But minification — renaming variables, tweaking control structures and whatnot — should happen at the module level because that’s faster and simpler.)

--

--

--

Journalist, ex software engineer

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Adam Hooper

Adam Hooper

Journalist, ex software engineer

More from Medium

Our relationship with $

7 Spiritual Laws of Prosperity for Personal Development — Life Change Plans

Begin Again…

Cracking the NIFT Recruitment Test