need to be able to run tests against classes, not just node js packages. Need this because we're currently can't run unit tests against client side classes (since they're trapped in the static folders)
use bugpack-registry to identify and find all the test classes (already have annotations for this)
Think we'll need bugjar for this...
Each bugjar should have a bugpack_registry.json file alredy generated for it
once the bugjar is installed, a new base registry would need to be generated that would have a list of sub registry files
bugjars will need to be able to indicate that they required a node js module to run and then will need to install that module at the top of the bugjar on install
during the install of an npm package, in order for us to successfully install the bugjars, we will need to provide a script in the package.json script list for the 'postinstall' hook. https://npmjs.org/doc/scripts.html
This script will be responsible for firing up the bugjar installer and installing the bugjars in to the freshly installed npm package.
we need to grab a list of bugjars from somewhere that the current npm modules depends on
in order to access bugjar from this script, we should be able to simply require it using node require('bugjar')
this system should be decoupled enough that bugjars should be able to be pre-installed in to a node js module. Perhaps this should be based on the 'bundle' parameter of npm?
Q:(how do we retrieve the name of the package that was just installed?)
A: Can retrieve this using the injected process.env variables
https://npmjs.org/doc/scripts.html#configuration
process.env.npm_package_name
Description
Q:(how do we retrieve the name of the package that was just installed?) A: Can retrieve this using the injected process.env variables https://npmjs.org/doc/scripts.html#configuration process.env.npm_package_name