Skip to content

The default of forceExclude is broken from Lambda with Node.js 18 runtime #361

@laurentperroteau

Description

@laurentperroteau

What is the problem ?

Using Node.js 18 and AWS SDK v3 significantly increases lambda size with defaults of serverless-bundle

Details :

From Node.js 18, the Lambda runtime layer include aws-sdk-js-v3 and the default forceExclude: [ 'aws-sdk'] is not working any more and should be replacer by the v3 package...

... but v3 is modular, and it's not possible to list the hundreds of packages. And because serverless-webpack do not allow regex or glob pattern, there is no workaround! On the other hand, it would be possible at least to prevent (see my PR).

Note: Personally, because I didn't know who excluded the "aws-sdk", it took me more than a day to solve the problem (first I searched for hours in the docs AWS, after in the Serverless docs and I finally found out it was serverless-bundle)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions