Skip to content
A new, faster way to build and share serverless applications.
Branch: master
Clone or download

Serverless Components

Updates ⚡️ v0.1.22 has been released - Includes the function & api provider agnostic components.

Serverless Components is a framework for provisioning and composing cloud services into higher-level abstractions, like features and applications. It depends on external Components, which are javascript libraries that can provision something, like infrastructure or a whole software feature built on multiple pieces of infrastructure.

You can use Components programmatically with a serverless.js file:

MyComponent extends Component {
  async default() {
    const website = await this.load('@serverless/website') // Load a component
    const outputs = await website({ code: './code' }) // Deploy it
    this.state.url = outputs.url

You can also use Components declaratively with a serverless.yml file:

name: my-app

  component: "@serverless/website"
    code: ./code
$ components # Run this CLI command to deploy



Getting Started

Install components.

$ npm i -g @serverless/components

create a directory for your new component.

$ mkdir my-component && cd my-component

Run components and choose what you'd like to create. Choose Create A New Component for a quick tour that helps you create your own component, which could programmatically use existing components from npm.

$ components

? Pick a starting point: (Use arrow keys)
❯ Create A New Component 
  Scheduled Task 
  Websocket Backend 
  Realtime Application 

Now every time you run components, you'll be running your new component. Check out the generated files for more information.

Instead of creating your own component, you could choose to generate a serverless.yml template that uses one or more of the available components (e.g. Chat Application template), which would copy one of the available templates into the current working directory. This time, everytime you run components, you'd be running this template.

Setting Credentials

When you're using or building components, you'll likely need provider credentials (e.g. AWS api keys), you can set credentials for each stage by creating .env files in the root of the directory that contains serverless.js or serverless.yml.

$ touch .env      # your development credentials
$ touch # your production credentials

the .env files are not required if you have the aws keys set globally and you want to use a single stage, but they should look like this in the case of AWS.


Programatic Usage

You can use any component programatically, while at the same time creating your own higher level component. All you need to do is:

Install @serverless/components as a local dependency.

npm i --save @serverless/components

Create a serverless.js file, extend the Component class and add a default method.

// serverless.js
const { Component } = require('@serverless/components')

class MyComponent extends Component {
  async default(inputs = {}) {} // The default functionality to run/provision/update your Component

default is always required. Other methods are optional. They all take an inputs object.

// serverless.js

class MyComponent extends Component {
   * Default (Required)
   * - The default functionality to run/provision/update your Component
   * - You can run this function by running the "components" command

  async default(inputs = {}) {}

   * Remove (Optional)
   * - If your Component removes infrastructure, this is recommended.
   * - You can run this function by running the "components remove"

  async remove(inputs = {}) {}

   * Anything (Optional)
   * - If you want to ship your Component w/ extra functionality, put it in a method.
   * - You can run this function by running the "components anything" command

  async anything(inputs = {}) {}

this comes loaded with lots of utilities which you can use.

class MyComponent extends Component {
  async default(inputs = {}) {
    // this.context features useful information

    // Get the targeted stage

    // Common provider credentials are identified in the environment or .env file and added to this.context.credentials
    // when you run "components", then the credentials in .env will be used
    // when you run "components --stage prod", then the credentials in will be used...etc
    // if you don't have any .env files, then global aws credentials will be used
    const dynamodb = new AWS.DynamoDB({ credentials: })

    // Save state = 'myComponent'

    // Load a child Component. This assumes you have the "@serverless/website" component
    // in your "package.json" file and ran "npm install"
    let website = await this.load('@serverless/website')

    // If you are deploying multiple instances of the same Component, include an instance id. This also pre-fills them with any existing state.
    let website1 = await this.load('@serverless/website', 'website1')
    let website2 = await this.load('@serverless/website', 'website2')

    // You can also load a local component that is not yet published to npm
    // just reference the root dir that contains the serverless.js file
    let localComponent = await this.load('../my-local-component')

    // Call the default method on a Component
    let websiteOutputs = await website({ region: 'us-east-1' })

    // Or call any other method on a Component
    let websiteRemoveOutputs = await website.remove()

    // Show status...

    // Show a nicely formatted log statement...
    this.cli.log('this is a log statement')

    // Show a nicely formatted warning...
    this.cli.warn('this is a log statement')

    // Show nicely formatted outputs at the end of everything
    this.cli.outputs({ url: websiteOutputs.url })

    // Return your results
    return { url: websiteOutputs.url }

Just run components in the directory that contains the serverless.js file to run your new component. You'll will see all the logs and outputs of your new components. Logs and outputs of any child component you use will not be shown, unless you run in verbose mode: components --verbose. You can also run any custom method/command you've defined with components <methodName>.

For complete real-world examples on writing components, check out our official components

Declarative Usage

If you want to compose some components together, without creating your own component, you can also do it declaratively, in YAML.

Create a serverless.yml file that looks like this.

name: my-stack      # a unique name to be reused
stage: dev          # a global stage to be reused
region: us-east-2   # a global region to be reused
anything: something # you can put any property here that could be reused.

# this property is identified as a component because it contains a component key
  component: "@serverless/aws-lambda" # the npm package name of the component that core would download and cache.

  # inputs to be passed to the component.
  # each component expects a different set of inputs.
  # check the respective docs of each component.
    name: ${name}-${stage}-lambda      # you can reference any property above
    region: ${region}                 # referencing the global region
      TABLE_NAME: ${} # you can also reference the outputs of another component in this file

  component: "@serverless/aws-dynamodb@0.1.0" # you could point to a specific npm version
    name: ${name}-table
    region: ${region}

# you could also use point to a local component directory with a serverless.js file
# very useful when developing & testing components
  component: "../my-component" # path to local component
    name: ${anything}-something

when you run components or components remove in the directory that contains the serverless.yml file, the core will set up a dependency graph based on your references and run the default function of each component in order. Only default and remove functions could be run when using serverless.yml. If you'd like to call a custom function of a component, use it programatically as explained above.


Created By

You can’t perform that action at this time.