JSPM

serverless-plugin-static-env

0.1.0
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 1424
  • Score
    100M100P100Q103093F
  • License MIT

Replace environment variables with static strings before deployment. It is for Lambda @ Edge.

Package Exports

  • serverless-plugin-static-env

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (serverless-plugin-static-env) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

serverless npm version License: MIT

Static Env ServerlessFramework Plugin

This plugin is is intended for use with Lambda@Edge to replace process.env and other similar mechanisms referencing environment variables with static values so that environment specific configuration can be used in Lambda@Edge (which does not support environment variables).

This is forked from serverless-plugin-embedded-env-in-code with the intention of taking a slightly different approach to the same problem.

This is work in progress, if you're looking for a working solution use serverless-plugin-embedded-env-in-code.

Approach Difference

Rather than using string substution, the intent is to load the module and replace it with a static version of it's exports using the built in serverless environment options.

The idea is this will provide a more consistent flow with other lambdas (specifying environment on the provider or function) and also allow less constraints on the configuration file.