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

inject-env-browser-run

v0.0.3

Published

It injects environment variables into your browser index.html

Downloads

7

Readme

inject-env-browser-run

It injects environment variables into your browser index.html

Why?

Browser doesn't have runtime access to the environment variables. So when we try to dockerize Frontend projects we intend to use --build-args to pass the variables to the image in build-stage. But this couples our images with environment it was built for.

For example: A project that requires an API_URL and will be deployed to dev, staging, qa and production environments will have to be built 4 times for every environment. Every time you release a new version of your application you will have to provide 4 different images.

More explantion:

Solution:

define your required variables. and inject this cli in your CMD and it will generate a file called env-config.js you could load into your html files and it will add an object called _env_ to your window object.

Install

$ npm install inject-env-browser-run

Demo

Check the demo/ folder for more guidance.

Config

You have to define a list of the required variables.

In package.json

"inject-env-browser-run": {
  "required": [
    "HOST",
    "BLOG_HOST",
    "DEBUG_LEVEL",
    "APP_TITLE"
  ]
}

Usage

const injectEnvBrowserRun = require('inject-env-browser-run');

injectEnvBrowserRun('src/foo/bar');
//=> 'creates an `env-config.js` file in the path src/foo/bar'

Then load env-config.js in your html file.

Note: don't bundle it in your JS bundle

API

injectEnvBrowserRun(dest)

dest

Type: string

the destination where the env-config file will be created

CLI

$ npm install --g inject-env-browser-run
$ inject-env-browser-run --help

	Usage
		$ inject-env-browser-run

	Options
		--dest  the destination where the env-config file will be created [Required]

	Examples
		$ inject-env-browser-run --dest src/foo/bar
    creates an `env-config.js` file in the path src/foo/bar