Debugging minified JS file is always a tedious task for developers. In day to day development life we end up in a situation where all JS files will be minified and moved into production for deployment. It is usual that some unprecedented JS error comes across browser versions. Being a developer finally it comes to our lap to resolve the issue. To reproduce the same error in a test environment with un-minified JS version doesn’t work out. To resolve this issue requires some kind of hard work which is time consuming.
Debugging a minified JS file is always a tedious task for developers. In day to day development life we end up in a situation where all JS files will be magnified and moved into production for deployment. It is usual that some unprecedented JS error comes across browser versions. Being a developer, finally it arrives in our laps to resolve the issue. To reproduce the same error in a test environment with un-minified JS version doesn’t work out. To resolve this issue requires some kind of hard work which is time consuming.
Smart work should be applied in this case. Everything has evolved, even browsers have evolved, understood the developer’s problem and gave unpaid feature called Pretty-Print.
We will look about this feature in the below steps,
Voice of a Developer: JavaScript From Scratch