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

@salesforce/plugin-evergreen-build

v0.20.8

Published

An SFDX CLI plugin for building and testing images for Salesforce Evergreen functions and services

Downloads

70

Readme

SFDX CLI Evergreen Build plugin

An SFDX CLI plugin for building and testing images for Salesforce Evergreen functions and service.

Note: This feature is in beta and has been released early so we can collect feedback. It may contain significant problems, undergo major changes, or be discontinued. The use of this feature is governed by the Salesforce.com Program Agreement.

oclif CircleCI Version Downloads/week License

Table of contents

Usage

$ sfdx plugins:install @salesforce/plugin-evergreen-build
running command...
$ sfdx evergreen --help [COMMAND]
USAGE
  $ sfdx evergreen:COMMAND
...

Commands

sfdx evergreen:function:build IMAGE

build function source code into a deployable image

USAGE
  $ sfdx evergreen:function:build IMAGE

ARGUMENTS
  IMAGE  image name, must be in all lowercase

OPTIONS
  -e, --env=env          Build-time environment variable, in the form 'VAR=VALUE'or 'VAR'. When using latter value-less
                         form, value will be taken from current environment at the time this command is executed. This
                         flag may occur multiple times if more than one variable is desired.

  -p, --path=path        [default: /home/circleci/project] path to function dir

  -v, --verbose          output raw build logs

  --buildpack=buildpack  Buildpack ID, path to a Buildpack directory, or path/URL to a Buildpack .tgz file. Repeat for
                         each buildpack in order.

  --clear-cache          Clear image's associated cache before building.

  --env-file=env-file    Build-time environment variables file comprised of one variable per line, of the form
                         'VAR=VALUE' or 'VAR' When using latter value-less form, value will be taken from current
                         environment at the time this command is executed.

  --network=network      Connect and build containers to a network. This can be useful to build containers which require
                         a local resource.

  --no-pull              Skip pulling builder and run images before use.

EXAMPLE

       $ sfdx evergreen:function:build image-repo/myfunction:dev
       $ sfdx evergreen:function:build image-repo/myfunction:dev --path /path/to/function/src
       $ sfdx evergreen:function:build image-repo/myfunction:dev --network host

See code: src/commands/evergreen/function/build.ts

sfdx run:function

send a cloudevent to a function

USAGE
  $ sfdx run:function

OPTIONS
  -H, --headers=headers                set headers
  -p, --payload=payload                set the payload of the cloudevent. also accepts @file.txt format
  -t, --targetusername=targetusername  username or alias for the target org; overrides default target org
  -u, --url=url                        (required) url of the function to run
  --structured                         set the cloudevent to be emitted as a structured cloudevent (json)

EXAMPLE

       $ sfdx run:function -u http://localhost:8080 -p '{"id": 12345}'
       $ sfdx run:function -u http://localhost:8080 -p '@file.json'
       $ echo '{"id": 12345}' | sfdx run:function -u http://localhost:8080
       $ sfdx run:function -u http://localhost:8080 -p '{"id": 12345}' --structured

See code: src/commands/run/function.ts

sfdx run:function:start

build and run function image locally

USAGE
  $ sfdx run:function:start

OPTIONS
  -d, --debug-port=debug-port  [default: 9229] port for remote debugging
  -e, --env=env                set environment variables (provided during build and run)
  -p, --port=port              [default: 8080] port for running the function
  -v, --verbose                output additional logs
  --builder=builder            set custom builder image
  --clear-cache                clear associated cache before executing.

  --network=network            Connect and build containers to a network. This can be useful to build containers which
                               require a local resource.

  --no-pull                    skip pulling builder image before use

EXAMPLE

       $ sfdx run:function:start
       $ sfdx run:function:start -e VAR=VALUE
       $ sfdx run:function:start --network host --no-pull --clear-cache --debug-port 9000 --port 5000

See code: src/commands/run/function/start.ts

Using a different builder

  • Grab the desired version from here, go get -u github.com/heroku/builder/cmd/builder, or build it yourself.
  • export BENNY_PATH=<path_to_built_binary>
  • Now you can run your sfdx commands that require a builder and it will use the provided builder instead of the one downloaded during plugin install.