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

cloudflare-workers-toolkit

v0.1.0

Published

A collection of useful resources for working with cloudflare workers

Downloads

8,206

Readme

Cloudflare Workers Toolkit

This library provides a simple integration to Cloudflare's APIs for resources applicable to Cloudflare Workers.

Multiscript versus Single Script

There are some subtle and not so subtle differences between Cloudflare accounts with multiscript enabled or not. By default, a standard Cloudflare account has single script enabled and an enterprise account has multi script enabled.

The subtle difference has to do with whether you deploy scripts by account or zone. The worker scripts take either an accountId (multi script) or zoneId (single script). When using an accountId, you must also specify a name for the script. You do not need to name a single script (zoneId) worker.

The not so subtle difference is that single script accounts use filters and multi script accounts use routes. Routes and Filters both use a URL pattern to control worker behavior. The difference is that filters control whether the single worker runs or doesn't run, whereas routes control which worker script is run.

Installation

npm install cloudflare-workers-toolkit

Initialize

const cloudflare = require("cloudflare-workers-toolkit");
cloudflare.setAccountId(accountId); // helper that sets an ENV var
cloudflare.setZoneId(zoneId);

Workers

Deploy a worker (will overwrite as well as create)

cloudflare.workers.deploy({
  accountId,
  name: "My Worker",
  script: "addEventListener('fetch', event => {
      event.respondWith(new Response(event.request));
    });",
  bindings: []
})
cloudflare.workers.getSettings()

Routes

Get all routes for a zone

cloudflare.routes.getRoutes({zoneId})

Remove a route

cloudflare.routes.remove({zoneId, routeId})

KV Storage Namespaces

cloudflare.storage.getNamespaces({accountId})
cloudflare.storage.createNamespace({accountId, name: "namespace name"})
cloudflare.storage.removeNamespace({accountId, namespaceId})

You can also pass name to remove. This method will look the id up for you before requesting the removal.

cloudflare.storage.removeNamespace({accountId, name: "my namespace name"})

Credentials

Cloudflare worker toolkit requires the following environment variables to be set:

CLOUDFLARE_AUTH_EMAIL
CLOUDFLARE_AUTH_KEY

Methods optionally take needed additional parameters, such as accountId. However, the following environment variables will be used as a fallback if set.

CLOUDFLARE_ACCOUNT_ID