excludeDevDependencies is not working when package points to parent directory

Are you certain it’s a bug?

• Yes, it looks like a bug

Is the issue caused by a plugin?

• It is not a plugin issue

Are you using the latest version?

• Yes, I’m using the latest version

Is there an existing issue for this?

• I have searched existing issues, it hasn’t been reported yet

Issue description

Serverless version: ^2.71.0

I decided to move my serverless.yml files into separated folder, and inside it point to the root folder:

|*root*
|-/infrastructure
|---serverless.yml
|-/src
|----*all code*

I can point serverless to include code from parent dir by using either include or pattern options in package section. However, in this case all node_modules gets included, even dev deps, even if you provide excludeDevDependencies: true in package section.

So I can either include all dependencies, or exclude entire node_modules, nothing more (obviously, I can manually exclude some node modules, but this would be hell).

Service configuration (serverless.yml) content

service: service-name
package:
  individually: true
  excludeDevDependencies: true
  include:
    - "../../../**/*"
  exclude:
    - "../../../tests/**"
    - "../../../infrastructure/**"

functions:
  processUpdate:
    name: function-name
    handler: ./src/lambdas/processUpdate.handler

Command name and used flags

serverless deploy

Command output

Output is normal deployment output, with huge s3 .zip file.

Also, i'm on Windows 10, and inclusion of all node_modules sometimes fails into "EMFILE: too many open files"

Environment information

Framework Core: 2.71.0 (local)
Plugin: 5.5.3
SDK: 4.3.0
Components: 3.18.1

[pgrzesik]

Hello @vssenko - thanks a lot for reporting. At the moment, exclusion of dependencies is always run against the node_modules placed in service directory, which in your case would be inside the infrastructure folder. I will bring this topic up during the internal meeting and will report back.

[vssenko]

Thank you all for being so responsive! I hope this new feature will be deployed soon!