npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

serverless-plugin-go

v0.0.3

Published

Serverless Framework plugin that compiles Go functions on the fly

Downloads

569

Readme

⚡️Serverless Framework Go Plugin

npm

serverless-plugin-go is a Serverless Framework plugin that compiles Go functions on the fly. You don't need to do it manually before serverless deploy. Once the plugin is installed it will happen automatically.

Features

  • Concurrent compilation happens across all CPU cores.
  • Support for both serverless deploy and serverless deploy function commands.
  • Support for serverless invoke local command.
  • Additional command serverless go build.

Install

  1. Install the plugin

    npm i --save-dev serverless-plugin-go
  2. Add it to your serverless.yaml

    plugins:
      - 'serverless-plugin-go'
  3. Replace every Go function's handler with *.go file path or a package path. E.g.

    functions:
      example:
        runtime: 'provided.al2'
        handler: 'functions/example/main.go' # or just functions/example

Configuration

Default values:

custom:
  go:
    # folder where go.mod file lives, if set `handler` property should be set relatively to that folder
    baseDir: '.'

    # Final target destination of the binary outputs
    binDir: '.bin'

    # Compile command that should be used to build binaries
    cmd: 'go build -ldflags="-s -w"'

    # If enabled, builds function every directory (useful for monorepo where go.mod is managed by each function
    monorepo: false

    # Number of concurrent process used to compile functions, you can fine tune this number to your needs.
    # Alternatively you can use the env var `SP_GO_CONCURRENCY` to override this configuration
    concurrency: 5

    # Environment variables used to compile binaries
    env:
      GOOS: 'linux' # Default compile OS
      CGO_ENABLED: '0' # By default CGO is disabled

How does it work?

The plugin compiles every Go function defined in serverless.yaml into .bin directory. After that it internally changes handler so that the Serverless Framework will deploy the compiled file not the source file.

For every matched function it also overrides package parameter to the next config:

individually: true
artifact: <path to the generated zip with go binary>

How to run Golang Lambda on ARM?

Change architecture field from provider or function configuration to arm64:

provider:
  architecture: 'arm64'
  runtime: 'provided.al2'

# If you define architecture at function level, this will have preference instead the provider configuration

functions:
  test:
    architecture: 'arm64'
    handler: test/main.go

Caveats

This implementation doesn't allow to add any other files to the lambda artifact apart from the binary. To address this problem you should use Lambda Layers to allow your lambdas to hold external files.

Credits

This repo is forked from serverless-go-plugin created by mthenw and modified to fix some issues and reach the new AWS standards (go1.x provider deprecation).