For my wireframe projects , usually monitoring, testing or services on the page to organize other toolboxes (but not as high as your number of files), my approach was aimed at separate and dynamically loaded files during development. For the test, I started one assembly for compression and version of individual files and checked individual files again, because, depending on the concatenation order, compression technique and browser, I can complete the script error, and itโs a pain to dig it out of one monster file. Thirdly, I will unite and try again.
In an HTML link, I will either target an uncompressed file that loads certain dependencies, or a compound file. A separate boot file names dependencies that are either included in the compound file or loaded dynamically as needed.
This way, I can add or modify the file and start development and testing without rebuilding.
Steve
source share