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

@urbanantics/environme

v1.0.21

Published

Build Utility, string replace based on environment configuration

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

rhuttonrhutton

Keywords

Readme

Description :

http://environ.me

Environ Me is a utiliy tool that can be run from the command line, which helps you better organise your static files, by allowing you to separate out and group the parts that change, and hopefully get more of your application configuration into source control.

It gives you:

  • a command line utility that can combine multiple files based on arguments and generate ouput files.
  • an npm package that can be used within your own code to produce the same merge functionality

Installation

Stable version:

npm i -g @urbanantics/environme

Usage :

Simple Example

Environme uses the following convention to locate static files and update their content

Suppose I had the following 2 files:

static-page.template.html

<!DOCTYPE html>
<html>
<body>
 <div>
   <img src="{$ config.url $}"/>
 </div>
  </body>
</html>

static-page.props.yml

config:
  url: https://www.petguide.com/wp-content/uploads/2019/05/meanest-cat-breeds-bengal.jpg
  TEST:
    url: https://www.petguide.com/wp-content/uploads/2013/05/pitbull.jpg
  PROD:
    url: https://www.petguide.com/wp-content/uploads/2013/02/dalmatian-11-475x421.jpg

Environme will look for files that have *.template in the name and then find the coresponding *.props.yml file, and use these 2 files to produce the corespondin output file

So say we have a file called static-page.template.html and props file called static-page.props.yml, and both are in the folder static-content, running the following command:

environme --path static-content/* --env PROD

will match:

  static-content/static-page.template.html
  static-content/static-page.props.yml

and produce the following file:

  static-content/static-page.html

with the folowing content:

<!DOCTYPE html>
<html>
<body>
 <div>
   <img src="https://www.petguide.com/wp-content/uploads/2013/02/dalmatian-11-475x421.jpg"/>
 </div>
  </body>
</html>
environme --path static-content/* -env TEST

will produce

and running the command with no --env will produce the default

environme --path static-content/*

Community :

Having problems? want to contribute? email [email protected]