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 🙏

© 2025 – Pkg Stats / Ryan Hefner

workers-metadata-types

v0.0.5

Published

TypeScript types for Cloudflare Worker configurations

Downloads

9

Readme

Flaredream Deploy

The simplest way to generate and immediately deploy a single-file worker.

1) Get your Cloudflare Credentials

  • Create an Account-Owned API Token here -> Create token -> Edit Cloudflare Workers
  • Visit https://deploy.flaredrea.com/login to login (Or pass Basic your account ID and API token as Basic Auth)

2) Add workers-metadata-types to your worker

  1. npm i --save-dev workers-metadata-types @cloudflare/workers-types
  2. add to your worker (either JS or TS)
/// <reference types="@cloudflare/workers-types" />
/// <reference types="workers-metadata-types" />
/// <reference lib="esnext" />
//@ts-check
/**
 * @type {import('workers-metadata-types').Metadata}
 * @see https://deploy.flaredream.com/index.d.ts
 */
export const metadata = {
  // configure your worker here
  // instead of in wrangler.toml
  // nothing is required
};

export default {
  /**
   * @param {Request} request
   * @param {{}} env
   * @param {ExecutionContext} ctx
   * @returns {Promise<Response>}
   */
  async fetch(request, env, ctx) {
    const url = new URL(request.url);
    // Your worker can use regular "export default" syntax
    return new Response("Hello, world!");
  },
};
  1. Submit your worker somewhere online on a public URL, e.g. https://raw.githubusercontent.com/janwilmake/xytext-tabs/refs/heads/main/tabs.js

Deployment

Visit https://deploy.flaredream.com/{YOUR_SCRIPT_URL}

System instructions for usage with lmpify.com or other LLMs

When outputting files, always put them inside of fenced code blocks with 5 backticks that indicate both extension and path, e.g.

console.log("hello,world!");
// A comment with backticks preventing from using 3 or 4 backticks: ````

Use tildes (~~~~~) instead of backticks for fenced code blocks when dealing with backtick-heavy content.

Incase you use LMPIFY, the generated worker will be available at https://{{prompt_id}}.gptideas.com/my-worker.js

After generation, let the user know to visit https://deploy.flaredream.com/{{prompt_id}}.gptideas.com/my-worker.js to deploy the worker. Please choose the filename carefully as this will be the name of the worker!