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

config-merge-loader

v1.0.0-beta.6

Published

Loader for mergeing environment specific localiztion or configuration into a base set at build time.

Downloads

5

Readme

config-merge-loader for Webpack

A webpack loader for merging configuration or localization files with a base set at build time. It should work with most loaders that generate JSON.

Installation

npm install config-merge-loader --save

Usage

This is intended to be used with loaders that poduce a JSON out put, like the json-loader itself or the yaml-loader.

Basic Usage

base.json:

{
  "a": 1,
  "b": {
    "a": 1,
    "b": 1
  },
  "c": 1
}

override.json:

{
  "a": 2,
  "b": {
    "a": 2
  }
}

webpack.config.js:

{
  …
  module: {
   rules: [
     {
       test: /\.json$/, use: 'json-loader'
     },
     {
       test: /base\.json$/,
       use: [
         {
           loader: 'config-merge-loader',
           query: {
             override: 'override.json'
           }
         }
       ]
      }
    ]
  }
  …
}

Then in your application code you can do the following

entry.js:

import config from './base.json'

const appConfig = JSON.parse(config);

console.log(appConfig);

Console result:

{
  a: 2,
  b: {
    a: 2,
    b: 1
  },
  c: 1
}

Usage With yaml-loader

base.yml:

a: 1
b:
  a: 1
  b: 1
c: 1

override.yml:

a: 2
b:
  a: 2

webpack.config.js:

{
  …
  module: {
    rules: [
      {
        test: /\.yml$/, use: [
          { loader: 'json-loader' },
          { loader: 'yaml-loader' }
        ]
      },
      {
        test: /base\.yml$/,
        use: [
          {
            loader: 'config-merge-loader',
            query: {
              override: 'override.yml'
            }
          },
          { loader: 'yaml-loader' }
        ]
      }
    ]
  }
  …
}

Then in your application code you can do the following

entry.js:

import config from './base.yml'

const appConfig = JSON.parse(config);

console.log(appConfig);

Console result:

{
  a: 2,
  b: {
    a: 2,
    b: 1
  },
  c: 1
}

Usage When Merging Different Namespaces

base.yml:

locale:
  a: 1
  b:
    a: 1
    b: 1
  c: 1

override.yml:

override:
  a: 2
  b:
    a: 2

webpack.config.js:

{
  …
  module: {
    rules: [
      {
        test: /\.yml$/, use: [
          { loader: 'json-loader' },
          { loader: 'yaml-loader' }
        ]
      },
      {
        test: /base\-namespace\.yml$/,
        use: [
          {
            loader: 'config-merge-loader',
            query: {
              baseNamespace: 'locale',
              override: 'override-namespace.yml',
              overrideNamespace: 'override'
            }
          },
          { loader: 'yaml-loader' }
        ]
      }
    ]
  }
  …
}

Then in your application code you can do the following

entry.js:

import locale from './base-namespace.yml'

const appLocale = JSON.parse(locale);

console.log(appLocale);

Console result:

{
  locale: {
    a: 2,
    b: {
      a: 2,
      b: 1
    },
    c: 1
  }
}

Options

override (required) string: Path to the override file. This will be merged in into the base file that is defined via an import or require statement.

baseNamespace (optional) string: the name of the key for the base object. This results in this name being kept in the output, and only it properties inside of it being updated.

overrideNamespace (optional) string: the name of top level key in the override object that will be used to override the base object.

Note: Currently baseNamespace and overrideNamespace can only select one level deep.