.env not evaluated in deeply-nested lambdas

[lukewpatterson]

Hi, I have a deeply nested lambda, e.g.

folder structure:   /aws_modules/cars/car/repairs/repair/invoices/invoice/GET
nesting level:    8 / 7         / 6  / 5 / 4     / 3    / 2      / 1     /.

( This example corresponds to a path along the lines of
GET /cars/{car}/repairs/{repair}/invoices/{invoice} )

The .env file isn't being evaluated and I think it's due to hardcoding a search depth of '6'

On the topic of "is deep nesting even supported in JAWS anyways?" -- I'm using serverless/serverless#135 as implicit confirmation.

For the moment I'll copy/paste/tweak/reference this libraries index.js file into my /lib folder.

Thanks!