Thomas Goirand <[email protected]> writes: > Web application have evolved into monsters that needs lots of > javascript. It's very common that these javascript applications are > collecting all the .js library they use, concatenate them into a > single file, and compress the result using all sorts of tools (node > uglify is one of the implementation, but that's not the only one).
My understanding is that the Debian JavaScript team is converging on a standard for compiling JavaScript (using uglify, I think) as a routine part of JS library package installation. How far along is such a rmalisation of convention? Is there a document yet discussing our consensus on JS compilation? > As much as possible, as good Debian citizens, we do package each and > every javascript library into a separate package. But then, if there's > an update of that JS library, the Web application package has to > somehow know about it, and redo the concatenate & compress job. > Otherwise, the web app would continue to use the old version. An alternative is that we standardise on *not* concatenating all the libraries together, but compile them so they're separate and modular. Would that be acceptable? -- \ “We suffer primarily not from our vices or our weaknesses, but | `\ from our illusions.” —Daniel J. Boorstin, historian, 1914–2004 | _o__) | Ben Finney _______________________________________________ Pkg-javascript-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
