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

envstachify

v1.0.1

Published

browserify transform to insert environment variables using mustache syntax

Downloads

4

Readme

envstachify

Evaluate files as mustache templates at build time, by default using process.env as the context. This is a lot like envify, but uses mustache-style syntax instead of process.env.VAR. This is NOT a mustache template compiler transform.

install

npm install --save-dev browserify envstachify

when and how to use

envstachify will replace {{ SOME_ENV }} or {{{ SOME_ENV }}} with the value of the SOME_ENV environment variable at build time. It's the same as envify, but it works on non-Javascript files.

If have some HTML for a template file that will be require()'d and needs to reference a URL that is only known at build time, envstachify has you covered. Here's a simple example using html-browserify to require html as a string:

// foo.js
var template = require('./templates/foo.html')
<!-- templates/foo.html -->
<img src="{{{ RELEASE_URL }}}/images/cat.jpg">
RELEASE_URL=http://example.com/builds/123 browserify -t html-browserify -t envstachify foo.js

foo.html will contain an image with src=http://example.com/builds/123/images/cat.jpg.