Load engines flexibly from either the current directory's node_modules

[geoffp]

@bmuenzenmeyer, check this out.

This should let us load engines from the core, or from whatever the "current" directory is. This isn't a perfect solution yet, because aside from checking the core, it assumes that the you're launching grunt/gulp/nodeunit/whatever from the root of your edition and looks for engine modules there. Has anyone ever not done it that way? Should we be more rigorous?

[bmuenzenmeyer]

Nice work Geoff!

[bmuenzenmeyer]

Has anyone ever not done it that way? Should we be more rigorous?

To answer your questions - no one has ever done what we are doing. Doesn't that sound dramatic! Using PL/Node core with a dependency + editions is new to the Node community, but the consumption patterns we are laying down cowpaths for now make a lot of sense, both for standalone (and perhaps) dependency consumption that we haven't imagined yet. We'll have to see I guess.