But when you deploy it’s not a clone.
Your production build is different from development stage. It’s not possible to diff them.
Perhaps live should be more similar to the development stage. In the world of security, a lot of resilience comes from people knowing their tools inside out. Having a development environment that is substantially different from the live environment is dangerous. That’s why we try to make the two as similar as possible. Ever heard of the guy who tested with an abstract encryption method, only to find out that in live deployed boxes the abstract method was implemented as the null encryption algorithm? The live boxes could talk to each other, no problem, likewise the test boxes, and all the test vectors checked out beautifully on the test boxes. Secure encryption that passes all the unit tests. Yay! Live might be different to the extent of minifying js but that should be about it.
It’s a little more than that, but not too much.
But if it was just that, you can’t diff minified and verbose code.
You can always use the --production flag in development:
--productionSimulate production mode. Minify and bundle CSS and JS files.
Doing that to get a diff-able codebase on both dev side and server side?
Seriously?
Best of luck with that. 
Well, no, I wouldn’t 
. But if someone was really inclined to try, it may be doable.
1 Like
That’s true, but why not upload the diff of the source code and build on the server?