Serverless Prune Path

This Serverless plugin allows you to optimize your AWS Lambda package before deployment by providing the ability to selectively prune your package. You can either specify paths to keep or paths to delete within the given directory.

The plugin works by first unpacking the Lambda package, pruning paths according to your specification, and then repackaging. This gives you greater control over your deployment package, especially when you are using custom packages or other packaging plugins.

This can be particularly useful when your project has dependencies or files that are not needed in the production environment, allowing you to reduce the size of your deployment package and ultimately the cold start time of your Lambda functions.

Prerequisites

Before using the serverless-prune-path plugin, make sure you have an existing Serverless project set up and Serverless Framework installed.

If you don't have the Serverless Framework installed, you can do so by running:

1npm install -g serverless

For more details on setting up a Serverless project and installing the Serverless Framework, please refer to the Serverless Framework Getting Started Guide.

How to Use

Installation

Install the plugin via npm:

1npm install --save-dev serverless-prune-path

Configuration

In your serverless.yml, add the plugin and configure your prunePath settings in the custom field:

1plugins:
2  - serverless-prune-path
3
4custom:
5  prunePath:
6    pathsToKeep:
7      all:
8        - 'path/to/keep/1'
9        - 'path/to/keep/2'
10    pathsToDelete:
11      all:
12        - 'path/to/delete/1'
13        - 'path/to/delete/2'

The pathsToKeep and pathsToDelete configuration options accept an object with a special keyword all. When you use 'all' as a key, it means that the array of paths you specify will apply to every single function in your service.

In this version, only the 'all' configuration is available for specifying the scope of pruning. That is, all the Lambda functions are targeted for pruning with the specified paths. Pruning individual functions is a feature planned for a future release.

Example

1custom:
2  prunePath:
3    pathsToKeep:
4      all:
5        - 'node_modules'
6        - 'handler.js'

In this example, 'node_modules' and 'handler.js' will be the only paths kept in every function's package. All other files and directories will be removed from the packages.

Likewise, if 'all' is used under pathsToDelete, the specified paths will be deleted from all function packages.

1custom:
2  prunePath:
3    pathsToDelete:
4      all:
5        - 'node_modules/aws-sdk'

In this example, 'node_modules/aws-sdk' will be deleted from every function's package.

Please note: Incorrect configuration may lead to the deletion of necessary files, causing your Lambda function to fail.

Prune Test

If you want to check the result of prune path, run the below command and check the packed lambda.

1serverless package

If you are happy with the result, and want to deploy

1serverless deploy

Future Work

We're always working to improve Serverless Prune Path and have some exciting features planned for the next version:

• Individual Function Pruning: We plan to introduce a feature to allow pruning paths for individual functions, giving you even greater control over your lambda packages.

README in Other Languages

• 한국어