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

wangler

v0.0.7

Published

Wrangler wrapper with .env file support

Downloads

621

Readme

wangler

Evil wrangler. A place for experiments by Sunil. Use at your own caution.

A wrapper around wrangler. For the lolz.

As of now, this adds just one feature: it automatically loads environment variables from .env files and populates process.env in your Cloudflare Workers.

Why

This is a feature that wrangler will eventually ship, but I wanted it now for my own stuff.

Installation

npm install wangler wrangler

Usage

  1. Create a .env file in your project root:
API_KEY=your-api-key
DATABASE_URL=your-database-url
  1. Use the wangler command instead of wrangler:
npx wangler dev # or wangler deploy
  1. Reference process.env/import.meta.env in your code:
console.log(process.env.API_KEY); // your-api-key
console.log(import.meta.env.DATABASE_URL); // your-database-url

Additional features:

  • These values are also injected into a request handler's env object.

  • You can pass a path to a custom .env file via --env-file <path>.

  • You can also have environment specific .env files. For example, you can have a .env.dev file for development and a .env.prod file for production. To use, pass --env <env> where <env> is the name of the environment you want to use. (This works with wrangler's own --env flag, where it'll pick bindings and values defined under [env.<env>] in wrangler.toml)

  • You can pass values in the cli via --penv <key>:<value>. This is useful for passing in arguments defined in your actual environment (like in CI, you can do npx wangler dev --penv DATABASE_URL:$SUPABASE_URL to pass in a value for DATABASE_URL).

  • You can pass values in the cli via --penv <key> to have the value be read from the environment. This is useful for passing in arguments defined in your actual environment (like in CI, you can do npx wangler dev --penv DATABASE_URL to have the value for process.env.DATABASE_URL be read from the environment).

How it works

This tool wraps the standard Wrangler CLI and automatically converts your .env file variables into --define arguments that Wrangler understands. It's a drop-in replacement for Wrangler that adds .env file support.

License

MIT