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

@helloample/netlify-plugin-replace

v1.1.4

Published

Replace strings in your publish directory

Downloads

151

Readme

netlify-plugin-replace

build status npm version

Replace environment variables in your publish directory before Netlify processes your build. Check out an example implementation here.

Why?

Netlify will deploy whatever you stick in your publish directory. This is great for simple use-cases but for projects that span multiple environments or rely heavily on environment variables, it can be tricky manage those differences without resorting to gnarly sed scripts or other unmentionable approaches.

This build plugin solves that problem by replacing references to environment variables after your project is built. A great example of this plugin's power is dynamically updating your _redirects file based on its deployment context.

Install

Add the plugin to your project's package.json file...

$ npm i @helloample/netlify-plugin-replace -D

Add the plugin to your project's netlify.toml file (see configuration for available options)...

[[plugins]]
  package = "@helloample/netlify-plugin-replace"

Commit & push changes back to your repository.

Usage

By default, this plugin will look for strings that match the following pattern...

${env:SOME_VALUE}

...and will attempt to replace that string with the value of the ENV variable by the same name. If the variable doesn't exist, it will not be replaced.

Following this example, any file in your build's output directory containing the string ${env:SOME_VALUE} will have that string replaced with the contents of process.env.SOME_VALUE when this plugin runs.

Configuration

This plugin offers some limited customization options as described below. Simply add these key/values to netlify.toml to customize the behavior for your needs.

  • delimiter: Regex pattern that tells the plugin how to find values to replace. Note, this pattern should contain a single capture group which encapsulates the entire name of the variable
  • fileTypes: Regex pattern defining the extension of the files to operate upon

The default configuration, if none is specified, is:

[[plugins]]
  package = "@helloample/netlify-plugin-replace"
  [plugins.inputs]
    delimiter = "\${env:([^}]_)}"
    fileTypes = ".*$"

License

This project is licensed under the MIT License.