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

@microbackend/plugin-env-vars

v1.0.1

Published

Micro-backend environment variables plugin

Downloads

6

Readme

@microbackend/plugin-env-vars

Microbackend plugin to inject environment variables into process.env.

Installation

npx microbackend plugin add @microbackend/plugin-env-vars

Usage

import createPluginConfig from "@microbackend/plugin-core/build/webpack.build";

await createPluginConfig({
  pluginOptions: {
    "@microbackend/plugin-env-vars": {
      additionalEnvVariables: { ENV_2: "2" },
      dumpToProcessEnv2: true,
      requiredEnvVariables: ["ENV_1", "ENV_2"],
    },
  },
});

The above configuration does the following:

  • Extract the environment variables in env.${environment}, where environment is determined by NODE_ENV. For example, if NODE_ENV is development, the values in env.development will be used.
  • Extract additional variables passed to additionalEnvVariables.
  • Check that the keys specified to requiredEnvVariables point to valid environment variable values. If they do not, an error will be thrown. This is useful for compile-time checks against missing environment variables.
  • Inject all the collected variables into process.env using DefinePlugin, which can be accessed during runtime using process.env.ENV1 (const { ENV_1 } = process.env will not work).
  • If dumpToProcessEnv2 is specified, dump all environment variables to process.env2 as well. This is useful during development when we want to view all currently available variables (e.g. console.log(process.env2)).