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

set-environment

v0.2.0

Published

Simple node script to change between frontend environment variables

Downloads

2

Readme

set-environment

Simple node script to change between frontend environments

Install

npm install set-environment

yarn add set-environment

Usage

Add envs folder to your root project folder (side by side with your package.json), then add your env files as you need e.g.

├── envs
│   ├── dev.json
│   ├── prod.json
│   ├── staging.json
│   └── test.json

then you need to add the env commands to your package.json scripts (note that the argument passed should be the same file name in your envs file)

"scripts": {
  "env:dev": "npm set-environment dev",
  "env:prod": "npm set-environment prod",
  "env:staging": "npm set-environment staging",
  "env:test": "npm set-environment test"
}

then, to change environments just:

npm env:dev
npm env:prod
npm env:staging
npm env:test