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

@utilities-studio/github-env

v1.0.1

Published

Load dotenv files into GitHub Actions environment and step outputs

Readme

github-env

Load dotenv files into GitHub Actions environment files.

bunx @utilities-studio/github-env --environment production
bunx @utilities-studio/github-env --environment production --outputs AWS_REGION,AWS_ACCOUNT_ID
bunx @utilities-studio/github-env --env-file config/smoke.env --outputs AWS_REGION
bunx @utilities-studio/github-env --env-dir apps/web --environment development --outputs VITE_SITE_URL

What it does

  • Resolves .env.<environment> when --environment is passed.
  • Falls back to .env only when no environment is passed.
  • Parses dotenv content as data with @dotenvx/dotenvx.
  • Writes all parsed application keys to $GITHUB_ENV.
  • Writes step outputs only when --outputs is passed.
  • Lowercases output names, so AWS_REGION becomes aws_region.
  • Fails when a requested output key is missing.
  • Fails closed for GitHub-reserved keys such as GITHUB_*, RUNNER_*, ACTIONS_*, and NODE_OPTIONS.
  • Can skip GitHub-reserved keys with --skip-reserved for deploy workflows that need to load mixed app/runtime env files.

Dotenvx metadata keys such as DOTENV_PUBLIC_KEY and DOTENV_PRIVATE_KEY are ignored.

GitHub Actions

- name: Load smoke env
  id: smoke-env
  run: >
    bunx @utilities-studio/github-env
    --environment "${{ inputs.environment }}"
    --outputs AWS_REGION,AWS_ACCOUNT_ID,VITE_SITE_URL

Later steps in the same job can use the loaded variables normally:

- name: Smoke test
  run: bun run smoke

Requested outputs are available from the step id:

- name: Configure AWS
  run: echo "region=${{ steps.smoke-env.outputs.aws_region }}"

Options

| Option | Description | | ---------------------- | ---------------------------------------------------------------------------------------- | | --environment <name> | Reads .env.<name> from --env-dir or the current directory. | | --env-dir <path> | Directory containing env files. Defaults to the current directory. | | --env-file <file> | Explicit env file to read, relative to --env-dir. Cannot be used with --environment. | | --outputs <KEY,...> | Comma-separated env keys to also expose as step outputs. No defaults. | | --skip-reserved | Skip GitHub-reserved env keys such as NODE_OPTIONS instead of failing. | | -q, --quiet | Suppress banner and success output. | | -v, --version | Print the package version. |

Security notes

Every value written to $GITHUB_ENV is available to later steps in the same job. Only use this in trusted workflows. Step outputs are allow-listed by --outputs and default to none.