Our app currently uses hundreds of small ("developer manageable") Javascript files.
Unfortunately, having so many files loaded by the client involves a lot of network overhead on the wire to communicate with the server.
We're looking into minifying our JS files into a single large file using the "Closure compiler" (https://developers.google.com/closure/compiler/) so we can have access to "Javascript Source Maps". To us, that would seem like the best of both worlds: always compact yet debuggable if/when needed.
I'd like to know if there are best practices we could adhere to in order to have "Closure Compiler" and Smartclient co-habit together.
Thanks !
Version: SmartClient 9.1p
Unfortunately, having so many files loaded by the client involves a lot of network overhead on the wire to communicate with the server.
We're looking into minifying our JS files into a single large file using the "Closure compiler" (https://developers.google.com/closure/compiler/) so we can have access to "Javascript Source Maps". To us, that would seem like the best of both worlds: always compact yet debuggable if/when needed.
I'd like to know if there are best practices we could adhere to in order to have "Closure Compiler" and Smartclient co-habit together.
Thanks !
Version: SmartClient 9.1p