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

@quark-fw/plugin-env

v0.1.32

Published

.env plugin for the Quark framework: every env var as an atom, live-reloaded via chokidar (published as raw TS sources; consumers run tsx)

Readme

@quark-fw/plugin-env

.env plugin for Quark apps: every environment variable is an atom (quark.env.get("KEY")), the .env file in the working directory is loaded on init and re-read when it changes (chokidar), and every change emits env:changed.

Install

npm i @quark-fw/plugin-env

Peer: @quark-fw/core.

Usage

import "@quark-fw/plugin-env"; // provides quark.env, watches ./.env

quark.env.get("FEATURE_FLAG").value; // Atom<string | undefined>, initial value from process.env
quark.env.has("REDIS_URL"); // true if seen by the plugin or present in process.env
const unsubscribe = quark.env.subscribe("FEATURE_FLAG", (value) => {
  /* reacts to .env edits at runtime */
});
quark.env.set("FEATURE_FLAG", "on"); // updates the atom and emits env:changed
quark.ee.value.on("env:changed", (key, value) => {});

How it works: atoms are created lazily per key with process.env[key] as the initial value. On init the plugin parses .env at process.cwd() (KEY=VALUE lines, # comments; the value is everything after the first =, trimmed, quotes are not stripped) and calls quark.env.set for each line, then watches the file (awaitWriteFinish) and reloads it on change. set() writes the atom only — process.env is not modified, so code that reads process.env directly keeps the startup value. The watcher is closed in onDestroy.

Env: no fixed names — the plugin reads process.env[<key>] for whatever key is requested, plus the ./.env file.

Part of the Quark framework.