You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched existing issues, it hasn't been reported yet
Issue description
I found the issue for devDependencies not being excluded for the parent directory issue, but we have our serverless.yml in the root, along with te node_modules.
We have had this working fine previously, and the deploy size of the Lambdas has been around 31 MB.
Now we hit 110 MB and the deploy fails as the unpackaged size exceeds 360 MB(!).
Extracting the ZIP I can see that all dependecises are there, e.g. serverless, aws-sdk, eslint etc.
### Command name and used flags
sls deploy -s test
### Command output
```shell
The verbose logging shows it is excluding dependencise:
stage: test
Packaging
Excluding development dependencies for function "migrator"
Excluding development dependencies for function "create-access-key"
Excluding development dependencies for function "integrationInternal"
Excluding development dependencies for function "integrationExternal"
Excluding development dependencies for function "internalRoutes"
Are you certain it's a bug?
Is the issue caused by a plugin?
Are you using the latest v3 release?
Is there an existing issue for this?
Issue description
I found the issue for devDependencies not being excluded for the parent directory issue, but we have our
serverless.yml
in the root, along with tenode_modules
.We have had this working fine previously, and the deploy size of the Lambdas has been around 31 MB.
Now we hit 110 MB and the deploy fails as the unpackaged size exceeds 360 MB(!).
Extracting the ZIP I can see that all dependecises are there, e.g.
serverless
,aws-sdk
,eslint
etc.What have I messed up?
Service configuration (serverless.yml) content
The text was updated successfully, but these errors were encountered: