Personally, I've switched to the OpenJSAN packaging standard.
It allows me to organize my js code in the packages and then having those packages installed in my system. So no more evil "include a copy of everything into each project".
JSAN distribution looks like:
Note unit tests.Code:|- lib/ |- Ext/ |- ux/ |- event/ |- Broadcast.js |- static/ |- whatever.. |- doc/ |- docs.. |- t/ |- 010_unit_test1.t.js |- 020_unit_test2.t.js |- 030_unit_test3.t.js |- README |- Build.PL |- MANIFEST
Examples of openjsan distributions:
After installation the example above will be copied into /usr/lib/local/jsan (or c:\JSAN on windows) as
OpenJSAN infrastructure is currently in alpha stage, so I'm not proposing it for everyone yet. After it will mature any OpenJSAN distribution will be installable locally with the command line:Code:|- lib/ |- Ext/ |- ux/ |- event/ |- Broadcast.js |- Broadcast/ |- static/ |- whatever..
(which will also issue a testing in all browsers available in the system)Code:jsan install My.JS.Distribution