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

@webscale-networks/cloudedge-handlers

v5.0.0

Published

Webscale Networks CloudEDGE Handlers for cloud-agnostic edge function execution

Downloads

21

Readme

cloudedge-handlers

This repository stores Webscale's cloudedge-handlers node module. This module has two primary responsibilities:

  1. To wrap CloudEDGE handlers, implemented as node modules, with a generic Webscale interface.
  2. Provide a testing framework for handler developers to ensure their handlers adhere to the interface and operate within the constraints of the runtime environment of their cloud providers. These tests are located in the execution_testing directory.

Unit tests

The repository's unit tests can be run with npm test. They are located in the execution_context directories.

How to use the handler testing framework

It is strongly suggested to run the provided unit tests in provided in execution_testing while a handler is developed. To do so, use the run-execution-testing.js as part of your package's NPM configuration and build process.

Publishing a new version

Before publishing a new version of this package, run npm audit to list any known security vulnerabilities. If found, run npm audit fix to address them and commit the resulting package.json.lock file.

Merging pull requests into the main branch will automatically run the package's unit tests and publish to NPM. If any unit test fails, the build will fail. To prevent this, run npm test locally before making a pull request ready for review.

Lastly, the version in package.json must be incremented according to semantic versioning. If this step is skipped, NPM will not publish the package's code changes.