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

taskforge-cli

v0.0.1

Published

A cli tool to leverage env related headache

Downloads

137

Readme

Why taskforge-cli

Have you ever been frustrated of changing env variable for stanalone projects, where no build tools are used, or doesnot support loading env variables out of the box, and you Have to use packages like dotenv.

One down side is that for each mode (development / test / production), you have to keep changing the values according to the mode. Well taskforge-cli lets you do that out of the box.

You can achieve this with the help of a config file tf.config.ts|js, and as well as cli options.

Config file

In config file you can defult export an Config object or a defineConfig() function which takes an object as a parameter or a function that returns an object as a parameter.

How to use it

// package.json

...
  "scripts": {
    "build": "tf build",                            // predefined script dev | build | test
    "foo": "tf custom foo",                         // custom script needs a "custom" keyword
    "bar": "tf custom bar",                         // custom script needs a "custom" keyword
    "bazz": "tf custom bazz --envFile ./.env.bazz", // custom script, loads ".env.bazz"
  },
...
export default defineConfig({
  scripts: {
    build: {
      execute: "node index.ts", // loads production env
    },
    foo: {
      execute: "node foo.ts", // loads ".env" by default unless specified
    },
    bar: {
      execute: "node bar.ts", // loads ".env.bar"
      envFile: "./env/.env.bar",
    },
  },
});

Options:

Config:

cli option: --config

alias: -c

type: string

defult: process.cwd()

If your config file is not at the root of your project, provide a relative path to the config file.

Env file:

cli option: --envFile

type: string

Pass a specific env file for that script.

Env directory:

cli option: --envDir

type: string

Pass a directory where your env files lives. It will load preferred env file depending on the script type.

If script is predefined i.e: dev | build | test, it will laod related env file, and if the script is custom it will load defult .env file.

Executing command:

cli option: --exec

type: string

Pass a command that should execute for that script.