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

@watchmen/cra-config

v1.1.2

Published

rich configuration for create-react-app

Downloads

3

Readme

cra-config

enable configuration containing complex javascript objects for create-react-app based applications

create-react-app has support for flat environment variables around a fixed set of predefined environments corrosponding to managed values of NODE_ENV, this may be sufficient for your use-cases.

if your requirements involve environments outside of those supported and/or you wish to work with rich javascript objects for configuration, then this package may be of value to you.

usage

  1. create a folder called config at the root of your project and place files in it with the format and naming conventions described below.

  2. in your package.json scripts, invoke the binary to generate the value for the REACT_APP_CONFIG environment-variable like so:

  "scripts": {
    "start": "REACT_APP_CONFIG=$(cra-config) react-scripts start",
    "build": "REACT_APP_CONFIG=$(cra-config) react-scripts build",
    "test": "NODE_ENV=test REACT_APP_CONFIG=$(cra-config) react-scripts test",
    "eject": "react-scripts eject"
  }
  1. in your code, import the cra-config module as below to reference the configuration values:
import React, { Component } from 'react';
import logo from './logo.svg';
import './App.css';
import config from 'cra-config';

class App extends Component {
  render() {
    return (
      <div className="App">
        <header className="App-header">
          <img src={logo} className="App-logo" alt="logo" />
          <p>
            Edit <code>src/App.js</code> and save to reload.
          </p>
          <a
            className="App-link"
            href="https://reactjs.org"
            target="_blank"
            rel="noopener noreferrer"
          >
            Learn React
          </a>
          <p>
            CONFIG = {config.someStringKey} // <--------------------- ta-dah!
          </p>
        </header>
      </div>
    );
  }
}

export default App;

format

module.exports = {
  someStringKey: "some-value",
  someIntegerKey: 123,
  someBooleanKey: true,
  someObjectKey: {
    someNestedStringKey: "some-nested-value"
  },
  someArrayKey: ["red", "white", "blue"]
};

{environment-name}.js

this file would contain values to be used when the environment-variable NODE_ENV is set to environment-name.

for example, lab.js would be used when the NODE_ENV environment-variable is set to lab

default.js

this file would contain values to be used across all environments, or those which should be defaulted if not provided in environment specific files.

the key/values in this file would always be present unless overridden by an environment specific file

local.js

this would be used to customize default values for local usage

add config/local.js to your .gitignore file