At the moment you can create a recipe for a Node.js module and its dependencies if you use npm to fetch the source, however if you point to a git repository or tarball of the source, it will recognise that it's Node.js code but doesn't know how to resolve the dependencies (since that his handled within BitBake's npm fetcher). We need to ensure the dependencies get brought in somehow. An example: https://github.com/01org/SmartHome-Demo We should also get to the point where creating the recipe for a module found through npm gives you pretty much the same built result (at least in terms of package names) as pointing recipetool at the git repository for that same module.
I hadn't intended to but I've pretty much ended up fixing this.
Merged to master: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=eb53750ab705bf340a588f91e3da3a1c81234e9b http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=5ab68677140ad6ffab7fbdeee6caeb19f4d80cba http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=3a0f5d95a7b6fc3557702c7fcd07ec64d37d2736 http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=fa90c2f54d7954dd3149404b38a0899d2e4962cf http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=ff259b095d1a84d1dc9b004c669c8f35659c3c2b