Installation & quick start

l is a CLI for maintaining AWS Lambda code from your terminal. This guide covers @ricko-v/l v2.0.0.

Prerequisites

• Node.js 22 or later and npm.
• A browser for AWS login.
• An AWS identity with permission to access the functions you want to manage.
• Existing Lambda functions with ZIP deployments for pull/push.

Install from npm

npm install -g @ricko-v/l
l --version
l --help

To update your installation, run npm install -g @ricko-v/l@latest again.

Sign in and check your identity

l login --profile production
l whoami --profile production

Complete AWS Sign-In in your browser, then wait for the final result in your terminal. Check Account and Identity before continuing. production is a local profile name; it does not determine which account you sign in to.

Create a project

mkdir billing-lambda
cd billing-lambda
l init --profile production

The wizard asks for a project name, resource region, and Lambda configuration. For your first run, select an existing function or enter its name manually. Review the JSON, then confirm saving l.config.json.

Example result:

{
  "version": 1,
  "name": "billing-lambda",
  "region": "ap-southeast-1",
  "profile": "production",
  "lambda": {
    "functionName": "billing-api"
  }
}

Replace the function name and region with your own target. Init saves local configuration; it does not create a Lambda function.

Pull code and preview changes

l lambda info
l pull --dry-run
l pull

Your code is available in lambda/billing-api/. Edit the files and prepare any build output your project needs, then preview:

l push --dry-run

When the target and changes look correct, run:

l push

Next steps

• Login & sessions: credential storage and signing in again after a refresh token expires.
• Multiple profiles: choosing a login per project.
• Pull & push: multiple functions, prefixes, ignore rules, backups, and conflicts.
• Command reference: all CLI options.