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 🙏

© 2024 – Pkg Stats / Ryan Hefner

from-env-with-expand

v2.1.0

Published

Drop in replacement for `from-env` with `dotenv-expand` preloaded

Downloads

6

Readme

🕶 from-env 🕶

from-env is helper script that makes environment variables from a local .env-file inside command line statements available.

Gitpod Ready-to-Code

installation

npm install --save-dev from-env-with-command

usage

.env

VARIABLE1=needs
VARIABLE2=have
VARIABLE3=variables

expansions inside .env

PORT=5000
PROTOCOL=http
HOST=localhost
URL=${PROTOCOL}://${HOST}:${PORT}

package.json (before)

{
    "scripts": {
        "yo": "your-command --that needs --to have --some variables"
    }
}

package.json (after)

{
    "scripts": {
        "yo": "from-env your-command --that %VARIABLE1 --to %VARIABLE2 --some %VARIABLE3"
    }
}

embedded variables replacement

To enable replacing variables that are not standlone:

from-env --embedded-vars your-command --things thing1=%VARIABLE1 thing2=%VARIABLE2 --other $VARIABLE3

or

from-env your-command --things thing1=%VARIABLE1 thing2=%VARIABLE2 --other $VARIABLE3

with

.env

FROM_ENV_EMBEDDED=true

alternative

this also works without any package (also on windows with wsl):

package.json

{
    "scripts": {
        "yo": "from-env your-command --that $(grep VARIABLE1 .env | cut -d '=' -f2) --to $(grep VARIABLE2 .env | cut -d '=' -f2) --some $(grep VARIABLE3 .env | cut -d '=' -f2)"
    }
}