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

extract-npm-package-config

v0.1.2

Published

Extract npm package config variables from process.env for in-app usage

Downloads

31

Readme

extract-npm-package-config

This package can extract npm package config variables from process.env for in-app usage.

Npm per-package configuration setting is an underrated feature.

https://docs.npmjs.com/misc/config#per-package-config-settings

package.json

...
  "config": {
    "scheme": "http",
    "domain": "localhost",
    "port": "3001"
  },
...
  1. As long as you use npm run ... scripts this config will be available in the process.env variables.
  2. Each of these variables can be referenced inside the package.json for usage with other scripts.
  3. Can easily be overridden via env variables server-side.

Install

npm install --save-dev extract-npm-package-config

Usage

Standalone

const packageConfig = extractPackageConfig(process.env);

npm_package_config_domain: 'localhost' npm_package_config_port: 3000

Webpack

It can easily be used in conjunction with webpack EnvironmentPlugin client-side.

webpack.config.js

...
plugins: [
    new webpack.EnvironmentPlugin(extractPackageConfig(process.env))
]
...

Note 1: You should'nt make use of it server side, because weback.DefinePlugin replace the variables in the source code itself, thus this would defeat the purpose of having env variables that can be easily overridden.

Note 2: There is currently a limitation due to the way weback.DefinePlugin replace process.env occurrences in the code. You can't destructure process.env see https://github.com/webpack/webpack/issues/5392

Licence

MIT