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 🙏

© 2026 – Pkg Stats / Ryan Hefner

wrangler-resolve

v1.0.0

Published

Cloudflare Workers integration for node-env-resolver (wrangler dev/deploy, FIFO secrets, hot reload)

Readme

node-env-resolver-cloudflare

Cloudflare Workers integration for node-env-resolver.

It provides:

  • wrangler-resolve CLI wrapper for wrangler dev, wrangler deploy, and wrangler types
  • Safe env injection for local dev via --env-file + FIFO on Unix
  • Deploy-time split of non-sensitive vars (--var) vs sensitive secrets (--secrets-file)
  • Explicit sensitivity support from schema validator metadata (for example secret()), with key-pattern fallback
  • Chunking support for serialized env blobs when secrets exceed Cloudflare's 5KB limit
  • A cf:// reference handler for resolving values from Workers env bindings
  • Resolver-driven watch graph support via resolver.metadata.watchPaths (with naming-convention fallback)

Install

npm install node-env-resolver-cloudflare

Peer dependency:

npm install node-env-resolver

CLI

npx wrangler-resolve dev
npx wrangler-resolve deploy
npx wrangler-resolve versions upload
npx wrangler-resolve types

All unrecognized commands are passed through to Wrangler.

CLI notes

  • dev refuses to run if .dev.vars exists, because wrangler-resolve manages env injection itself.
  • deploy manages --secrets-file automatically; do not pass --secrets-file manually.
  • Set NER_CF_DEBUG=1 to enable debug logging.

Custom config

By default, the CLI uses processEnv() as the resolver source.

To provide custom resolvers, set NER_CF_CONFIG to a module path that exports WranglerFacade options:

// wrangler-resolve.config.ts
import { dotenv } from 'node-env-resolver/resolvers';

export default {
  resolvers: [[dotenv('.env.local'), {}]],
  watchPaths: ['.env.local', '.env.local.secrets'],
};
NER_CF_CONFIG=./wrangler-resolve.config.ts npx wrangler-resolve dev

Programmatic usage

import { WranglerFacade } from 'node-env-resolver-cloudflare';
import { dotenv } from 'node-env-resolver/resolvers';

const facade = new WranglerFacade({
  resolvers: [[dotenv('.env.local'), {}]],
});

await facade.dev();

Watch strategy

When watchPaths is not provided, you can control auto-detection:

const facade = new WranglerFacade({
  resolvers: [[dotenv('.env.local'), {}]],
  watchStrategy: 'auto', // 'auto' (default) | 'metadata' | 'fallback'
});
  • auto (default): use resolver metadata/naming-derived paths, fallback to .env, .env.local, .env.development, .env.development.local if none found.
  • metadata: use resolver-derived paths only (no fallback).
  • fallback: ignore resolver metadata and use .env, .env.local, .env.development, .env.development.local.

cf:// handler

import { createCloudflareHandler } from 'node-env-resolver-cloudflare/handlers';

const handler = createCloudflareHandler({ env });
// resolves values like cf://MY_SECRET from Workers env bindings

Exports

  • node-env-resolver-cloudflare
  • node-env-resolver-cloudflare/handlers
  • node-env-resolver-cloudflare/wrangler
  • node-env-resolver-cloudflare/chunking
  • node-env-resolver-cloudflare/fifo