After npm install in the Well dir, seneca-crypto-sign@0.1.1 is installed under seneca-auth, but the server fails at startup with an error that it can't find seneca-crypto-sign.
Modifying Well/package.json to add seneca-crypto-sign@0.1.1 as a dependency seems to resolve this error at startup, but I don't know if this is the correct solution.
After npm install in the Well dir, seneca-crypto-sign@0.1.1 is installed under seneca-auth, but the server fails at startup with an error that it can't find seneca-crypto-sign.
Modifying Well/package.json to add seneca-crypto-sign@0.1.1 as a dependency seems to resolve this error at startup, but I don't know if this is the correct solution.