Need private packages and team management tools?Check out npm Orgs. »


1.0.2 • Public • Published


Build Status Coverage Status


A simple webpack loader to load and customize application settings based on the provided environment.


We often specify the application settings in a JSON file and use it during development; something like below, for example.

    "debug": true,
    "endpoint": "http://localhost:8080/",
    "basePath": "api/"

However, for production (or any other environment) we may need different settings/values for a subset of keys. For example,

    "debug": false,
    "endpoint": "http://my.awesome.service/",

Using this loader, you can bundle environment specific values, given 2 JSON files exist.



npm i -D app-settings-loader


Let us assume that we have following directory structure.

| |
| +-appConfig.json
| +-appConfig.development.json

Then you use the appConfig.json in main.ts as follows.

// with "resolveJsonModule": true in your tsconfig
import * as config from "./config/appConfig.json";
// or
const config = require("./config/appConfig.json");

In your webpack add the loader as follows.

    test: /appConfig\.json$/i, // change this as per your file name
    use: [
        { loader: "app-settings-loader", options: { env: production ? 'production' : 'development' } },

With the above config, the loader will merge the customization coming from the appConfig.development.json with the base config in appConfig.json, when production is truthy.

How does it work

The loader has only one option env (environment, default value is "development"). If the base JSON file name is mysettings.json, it looks for a JSON file named mysettings.{env}.json at the same directory path. If there is one, it merges the customization form that file with the base file, and returns the result. In case there is no customization file, it returns the base content. Note that if you want you may have more environment names, as per your need. That is you may set env as Betelgeuse5, and provided you have a JSON for that, it will load that too :)


  • Merging configurations: The merge operation keeps the schema of the base file intact. That is, no unknown properties or property value of different type, from the customization files can be applied on the base file. This makes sense because during development you expect a certain set of keys and values of certain datatype to be present in your config and you program against this known schema. Therefore any new keys present in the customization file cannot and should not play any part in the source code.
  • Valid JSON: The content of the both base and customization file needs to be valid JSON. Otherwise, it will throw an error.
  • Do not store sensitive data: As the config will be part of webpack bundle, you should not store any sensitive data in the customization file. The thumb rule is that any sensitive data that you don't want to keep in your source code, should also not be the part of either base or customization config file.

That's it. If you face any problem, feel free to open an issue.


npm i app-settings-loader

Downloadsweekly downloads









last publish


  • avatar
Report a vulnerability