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

crds-components-env-replace

v1.0.1

Published

Utility to swap environment values following an SPA build process.

Downloads

2

Readme

crds-components-env-replace

This project is a command-line utility for replacing environment-specific values that reference crds-componentsin the index.html file of a built SPA project.

Installation

Since it's run immediately after build, it works best in you can bundle the script within your project. But this project is only available via GitHub. Therefore, this is how you install via npm:

$ npm install --save-dev crdschurch/crds-components-env-replace#master

Usage

Basic usage looks like this:

$ crds-components-env-replace [options]

If using as part of your project, add the script to the scripts section in your package.json file:

{
  "...": "...",
  "scripts": {
    "...": "...",
    "env:replace": "crds-components-env-replace [options]"
  }
}

You would then be able to run the script like so:

$ npm run env:replace

Options

The following options are available:

| Variable | Default | Description | | -------- | ------------------- | --------------------------------------------------- | | env | int | The environment for which values should be adjusted | | file | ./dist/index.html | The file containing reference to crds-components |

Note the following:

  • The script does nothing if left in the int environment (see Environments, below), as it is assumed all default values in your index.html file are specific to int.
  • Only certain environments are accepted. See below for the list.
  • The file should point to your built index.html file. While this defaults to the typical ./dist/index.html location, it is recommended you specify this directly. This argument is passed to the replace-in-file utility, which supports globs.

Given those notes, if you are using $CRDS_ENV to specify your environment, then your usage will look something like this:

$ crds-components-env-replace --env $CRDS_ENV --file ./dist/index.html

Environments

Only certain permuations of each environment are available and accepted by the script. See the chart for details:

| Environment | Permutations | | ----------- | --------------------------- | | int | int, dev, development | | demo | demo | | prod | prod, production |

License

This project is licensed under the MIT License.