bergie/noflo — pull request #83 by kenhkan (2013-06-03 09:11:45+00:00)
Title: Avoid loading custom packages' names

I don't know whether this is a problem for anyone or what causes this. When I'm extensively linking various noflo packages locally for development, noflo would fetch a "null" dependency so that the sub-modules callback would receive a `null` for `def`, rendering an error. This issue only happens when packages are linked using `npm link`.