New answers tagged

0

I've come up with another solution that I think may work. For all of the .js files that we've currently got in a working directory (e.g. "script_dir"), we maintain the original code with meaningful symbols in a source directory (e.g. "script_dir_source"). The build process copies all of the .js files from the source directory to the working directory, then ...


1

There are a few considerations to take into account. Even unused constants will take up memory and processing time on the client's browser. How much of an issue this might be depends on how many of those unused constants you have and how many resources (memory and CPU power) your clients are expected to have. Everything you send in JavaScript should be ...


Top 50 recent answers are included