[patch] Use node module resolution properly

[Swatinem]

For quite a few cases, sails does not use the default node module resolution algorithm, but builds explicit paths in ${appPath}/node_modules/, which is not nice.

[sailsbot]

Thanks for posting, @Swatinem! We'll look into this ASAP.

---

For help with questions about Sails, click here. If you’re interested in hiring @sailsbot and her minions in Austin, click here.

[mikermcneil]

@Swatinem Why do you feel that this is not nice? (There's a reason we do it this way.)

[Swatinem]

We have multiple sails apps inside a mono-repo, and would like to hoist some dependencies to the toplevel.
We worked around this problem anyway by just creating symlinks where needed.

[tomasfrancisco]

I might have the same problem.

I'm trying to set up a mono repo with yarn workspaces and I'm getting the following error when I try to run sails:

Failed to lift app: TypeError: Cannot read property 'readJson' of undefined
    at Object.module.exports.bootstrap (/Users/tomasfrancisco/Documents/dev/example-project/api/config/bootstrap.js:53:8)

@Swatinem Can I ask you what exactly did you do to fix it?

[Swatinem]

Well you can:

• use the nohoist feature of recent yarn > 1.5 to exclude certain things from hoisting
• manually create symlinks from /packages/$FOO/node_modules/$BAR -> /node_modules/$BAR

We went the symlink route because yarn still hoists your workspace packages themselves, and we needed those because some of them were sails hooks.

So you want to nohoist:

• connect-redis
• sails-mysql (or equivalent)
• anything that is a sails hook. Sails basically enumerates every package in ./node_modules/… and looks at the package.json to figure out if its a hook or not (please correct me if I‘m wrong)