node-config

Node.js Application Configuration (by node-config)

Node-config Alternatives

Similar projects and alternatives to node-config

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better node-config alternative or higher similarity.

node-config reviews and mentions

Posts with mentions or reviews of node-config. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-10-03.
  • topoconfig: enhancing config declarations with graphs
    10 projects | dev.to | 3 Oct 2023
    node-config
  • How We Converted a GitHub Tool Into a General Purpose Webhook Proxy to Supercharge Our Integration Development
    10 projects | dev.to | 21 Apr 2023
    This will allow to set a security operation mode and configure the channels. I chose to use the config package as I had good experience with it and it supports cascading config options.
  • Tailwind CSS: Using dynamic breakpoints and container queries
    2 projects | dev.to | 23 Feb 2023
    Tailwind CSS v3.2.4 includes a new @config directive that lets you specify which Tailwind CSS config to use for that file.
  • Managing Your Distributed Node.js Application Environment and Configuration
    2 projects | dev.to | 19 Oct 2022
    In this article, I'm going to demonstrate how the dotenv and node-config NPM packages can be used together to keep your Node.js application code organized across environments.
  • NextJS - Get rid of DotENV
    2 projects | dev.to | 31 Mar 2022
    I always disliked the .env file. Almost every time I was forced to place it on the top level of my app directory. At some point i started to use the npm config package. This gives the application a consistent configuration interface and there is a formidable way to implement it into the NextJS environment. For people which prefer code over text, feel free to checkout the finished implementation.
  • Advice for writing enterprise-level API in Go?
    8 projects | /r/learngolang | 18 Dec 2021
    How do I handle configs? In our Node APIs we use this config package, which allows us to override default configs on a per-environment basis. What's the standard way of doing this in Go?
  • The Perfect Configuration Format? Try TypeScript
    17 projects | news.ycombinator.com | 17 Nov 2021
    I have used TypeScript for config in a few projects, with node-config[1], and it’s substantially better IME than JSON/YAML/etc. Yeah it’s unconventional to write configs in a general purpose language, and I understand why that would be undesirable. But having configs validated at compile time is great at preventing bugs.

    I’m not sure I’d recommend node-config (it was chosen by a past team). Its magic undermines the confidence in type safety provided by choosing TypeScript in the first place. But it does give some good baseline conventions one can apply without all the magic.

    1: https://github.com/lorenwest/node-config

  • Serverless functions with FN project
    3 projects | dev.to | 6 Oct 2021
    docker run --rm -it --link fnserver:api -p 4000:4000 -e "FN_API_URL=http://api:8080" fnproject/ui Unable to find image 'fnproject/ui:latest' locally latest: Pulling from fnproject/ui b56ae66c2937: Pull complete e93c4ef66dd7: Pull complete a9e499bf0a12: Pull complete ba1608f40908: Pull complete 6464d2649fbf: Pull complete ebc7db4cf098: Pull complete f34c1cd5ef21: Pull complete dc688e6ebaad: Pull complete Digest: sha256:82c5b2fd02d702d2294bb107c1c022dba699241f64e4e14b77519d4c25bbb5f9 Status: Downloaded newer image for fnproject/ui:latest > [email protected] start /app > node server WARNING: NODE_ENV value of 'production' did match any deployment config file names. WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode info: Using API url: api:8080 info: Server running on port 4000
  • A simple configuration file loader and compositor utility.
    3 projects | /r/node | 1 Sep 2021
    Looks like the config module, but more steps needed to make it work. Is there anything that makes your module the better solution for your problem?
    3 projects | /r/node | 1 Sep 2021
    Thank you for your detailed answer. I think you did miss the correct approach to using ENV vars in the config module, which would be to have a separate file called 'custom-environment-variables.json' that maps your environment variables to the right property. For example: config/default.js module.exports = { db: { user: 'dev-user', password: '123456', host: 'db', name: 'application' } } config/custom-environment-variables.json { "db": { "user": "DB_USER", "password": "DB_PASSWORD", "host": "DB_HOST" } } db.js const dbConfig = require('config').get('db'); console.log(dbConfig); Run: DB_USER=prod-user DB_PASSWORD=abcdef DB_HOST=prod node db.js Output: { "user": "prod-user", "password": "abcdef", "host": "db", "name": "application" } Config composition is actually configs greatest feature I would say. Though the priority chain in the config module is hardcoded (see: https://github.com/lorenwest/node-config/wiki/Configuration-Files), while in yours you can actually which source takes priority.
  • A note from our sponsor - InfluxDB
    www.influxdata.com | 29 Mar 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →

Stats

Basic node-config repo stats
20
6,187
5.7
about 2 months ago
Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com