I am trying to understand JavaScript minification and pression processes and have couple of questions on these:

1. Since minification makes the code difficult to debug, is it possible to do on-demand de-minification on client-side to cover-up for cases where you actually need to debug and investigate something on the website?
2. I remember reading somewhere that one can enable pression of all resources (like images, CSS, JavaScript etc.) by setting some options in the Apache Web Server. Is there any difference in the JavaScript pression done at Apache level and, the one done using tools like YUI Compressor?

Can someone help me know the above?

The kind-of cases where I would actually need to de-minify my JavaScript files is let's say a JavaScript error happened at line no. X. With a minified files it would be very tough to know which block of code caused that error in production as the lines are all wrapped up in a minified file. How do you guys investigate and debug in such circumstances? Another user also mentioned this debugging problem in Packed/minified javascript failing in IE6 - how to debug? questions (slightly specific to IE6 though).

I am trying to understand JavaScript minification and pression processes and have couple of questions on these:

1. Since minification makes the code difficult to debug, is it possible to do on-demand de-minification on client-side to cover-up for cases where you actually need to debug and investigate something on the website?
2. I remember reading somewhere that one can enable pression of all resources (like images, CSS, JavaScript etc.) by setting some options in the Apache Web Server. Is there any difference in the JavaScript pression done at Apache level and, the one done using tools like YUI Compressor?

Can someone help me know the above?

The kind-of cases where I would actually need to de-minify my JavaScript files is let's say a JavaScript error happened at line no. X. With a minified files it would be very tough to know which block of code caused that error in production as the lines are all wrapped up in a minified file. How do you guys investigate and debug in such circumstances? Another user also mentioned this debugging problem in Packed/minified javascript failing in IE6 - how to debug? questions (slightly specific to IE6 though).

• javascript
• minify
• http-pression

6 Answers 6

You shouldn't be debugging minified code. Ideally, development process is like this:

1. You build and debug the site locally. You have full versions of javascripts, stylesheets and everything.

2. You deploy a version to production machine. You minify and gzip a copy of your assets and push that to the server. Your local development copy is left untouched.

3. If there's a bug in production, you modify your local version, minify, press, upload.

Repeat until PROFIT

Chrome Dev Tools can de-obfuscate (and de-minify) javascript code if you want to debug production code (useful when trying to replicate a bug on a live environment you may not be seeing in dev)

Typically developers will develop against the unpressed script file, press right before deploying.

If you have to go back and debug your script files, you'd just open up the regular, unpressed file, do your work, press, and deploy. If you mean debug something while your website is in production, then no, you can't un-minify your script file on demand.

And yes, Apache, and even IIS, can gzip press scripts and images automatically for you.

Since minification makes the code difficult to debug, is it possible to do on-demand de-minification on client-side to cover-up for cases where you actually need to debug and investigate something on the website?

Sort of. Minified javascript has the same structure, it just does things like delete extra spaces and shorten variable names. So you can easily make the code readable again, either manually or with a script, but you can't recover variable names, so the code will still be harder to work with. So, if you have the original code, definitely don't get rid of it. Save the minified code separately.

I remember reading somewhere that one can enable pression of all resources (like images, css, javascript etc.) by setting some options in the Apache Web Server.

Yes, it's called gzip pression. It's not unique to apache, but you would need to configure your server to enable it.

Is there any difference in the javascript pression done at Apache level and, the one done using tools like YUI Compressor?

Yes. YUI pressor is a minifier - the output is valid javascript. Server-side pression is more analogous to zipping a file - the browser must decode it before it can be used. Using the two together would yield the smallest filesize.

1. I prefer working with a local unminified copy of the JS-file, and when i deploy the site, I minify all JS-files into one. That way it is easy to debug and improve the code. However, there are tools to revert minification. Have a look at this SO post on revert minification of JavaScript.
2. Have a look at GZIP pression - This blog describe how to enable GZIP in Apache and how to verify that your server actually is pressing the files.

is it possible to do on-demand de-minification on client-side

Some browsers have a "pretty code" view that automatically formats source code. See Firebug's CSS tab.

Is there any difference in the javascript pression done at Apache level and, the one done using tools like YUI Compressor?

YIU Compressor is a actually a minifier. Apache pression is like ZIP-ing up the file before it is sent to the client so the actual file that is sent is smaller than the file on disk. They are two different technologies that are independent of each other.