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

shell-script-reader

v0.1.0

Published

shell-script-reader

Readme

Build Status

Coverage Status MIT license

Shell Script Reader

Shell Script Reader provides a way to read user customized shell script where a lot of enviromental vairables are defined.

So you can easily share your shell variables with your node.js scripts.

Instead of using a central process.env, you can use your enviromental variable sets for each projects respectively. These way you will be eased by multiple projects and tests for various configurations.

And still you can easily interacting with shell vairaibles.

Install

npm install --save shell-script-reader

Usage

Import

import { ShellScriptReader } from "shell-script-reader";

Initialize

import * as path from "path";
const filename = path.resolve(__dirname, "./env");
const reader = new ShellScriptReader(filename);

env file example:

export AAA=111
export BBB=sosoisidoeod
export ENV=E-SS OS
export UN=
export UN=aaasossos=aaa
export AAAAA
export
export

# SHELL COMMENTS
wget https://www.google.com

Only ^export stated lines are read.

We will have an env object:

    { AAA: '111',
      BBB: 'sosoisidoeod',
      ENV: 'E-SS OS',
      UN: '',
      AAAAA: '' }

Read process.env

It provides access to process.env for convenience sake.

const value = reader.getEnvRaw("KEY_NAME");

Read Script Variables

const value = reader.getEnv("KEY_NAME");

For ./env script defined above:

const value = reader.getEnv("AAA");
// '111'
const value = reader.getEnv("BBB");
// 'sosoisidoeod'

If no key is provided, the whole object will be returned:

const value = reader.getEnv();
// { AAA: '111',
//   BBB: 'sosoisidoeod',
//   ENV: 'E-SS OS',
//   UN: '',
//   AAAAA: '' }

License

The MIT License (MIT)