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

envland

v0.1.5

Published

CLI for syncing .env files with the Envland console

Downloads

906

Readme

envland CLI

Sync .env files with envland.dev.

Install

npm install -g envland

Usage

envland login          # authenticate via browser
envland init           # link cwd to a project (.envland.json)
envland pull [env]     # download secrets into .env
envland push [env]     # upload local .env (shows diff, confirms)
envland diff [env]     # compare local vs remote
envland run [env] -- <cmd>   # run a command with secrets injected
envland open           # open project in the console

At runtime, override with ENVLAND_API_URL. The default is baked in at build time (see below).

Develop

From the monorepo root:

bun --filter envland build        # bundle for npm (dist/envland.js)
bun --filter envland build:binary # native binary (dist/envland)
node apps/cli/dist/envland.js help

Build-time API URL

bun run build bakes https://api.envland.dev as the default API host. For local dev:

bun run build:local   # http://localhost:4001

Override for a one-off build:

ENVLAND_API_URL=https://api.envland.dev bun run build:bundle

prepublishOnly runs build automatically on npm publish.

Publish

  1. Bump version in apps/cli/package.json.
  2. Commit and push a tag: git tag cli-v0.1.0 && git push origin cli-v0.1.0
  3. GitHub Actions publishes to npm (requires NPM_TOKEN repo secret).

Manual publish (runtime deps are bundled — do not add workspace:* to dependencies):

cd apps/cli
npm login
npm publish --access public