Eyeglass import fails when nearest package.json doesn't contain eyeglass module

Nobody has claimed this yet.

I thought the recent Windows bug was effecting my imports but now I understand that having multiple package.json files causes eyeglass modules to not be found.

Given the following structure:

```
package.json
gulpfile.js
Styles/
microsite/
|--Styles/
|--package.json
|--gulpfile.js
shared_feature/
|--Styles/
|--gulpfile.js

```

Eyeglass modules are declared in the root package.json file.
Styles built with the root folder gulpfile will see Eyeglass modules.
Styles built in: a folder where a package.json exists; or at a level below a package.json that isn't the root package.json (where Eyeglass modules are defined) will not recognize the Eyeglass modules.

Reproduce the issue with the shown nested package.json and gulpfile.js layout, comparing a root build with one started below another package.json. Start by tracing how the gulpfile locates package.json and Eyeglass modules; done means nested builds recognize modules declared in the root package.json without breaking existing root builds.

Written by the indexing model from the issue text.