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

@digitalocean/functions-deployer

v5.0.20

Published

The the functions deployer for DigitalOcean

Downloads

10

Readme

DigitalOcean Functions deployer library (Node.js)

This repository contains an internal TypeScript library for deploying functions in DigitalOcean. It is used by the doctl serverless deployer plugin and in remote builds.

The contents were jumpstarted by migrating the original Nimbella deployer from nimbella/nimbella-deployer. The commit history (and version history) was preserved. Thus, the first version sourced from this repo is a new major version, 5.0.0.

There are three artifacts that are derived from this source:

  1. A nodejs library for incorporation into other node-based tools. Currently, this is uploaded to a DigitalOcean space object store for later incorporation but it should eventually be published to npm.
  2. The doctl serverless deployer-plugin. Currently, this is built from (1) in the separate repo digitalocean/doctl-sandbox-plugin.
  3. An install image for installing the deployer into container images (currently just runtime containers) with an outer shell called dosls. We do not install a complete doctlinto those images unless it is needed for another purpose.

Artifacts (1) and (3) are built by the script internalRelease.sh with no arguments. That script is driven by a GitHub action on every push to the main branch. It only builds the artifacts if the current version (in package.json) is not yet uploaded to the tools Space. After building the artifacts, it uploads them as well. So, new versions are "published" only on pushes to main with a new version number.

The internalRelease.sh script can also be run with a --test flag, in which case is builds the artifacts unconditionally but does not upload them.

Testing changes locally

To test changes locally

npm install
npm run build

after which the deployer shell can be run as /path/to/repo/bin/run. It is often convenient to make a symbolic link in your path pointing to that location (e.g. as dosls). Then, you can test with

dosls deploy <projectDir>
dosls get-metadata <projectDir>
dosls watch <projectDir>