@Sugoi\core
node-config
@Sugoi\core | node-config | |
---|---|---|
- | 20 | |
7 | 6,203 | |
- | 0.3% | |
0.0 | 5.0 | |
over 1 year ago | 14 days ago | |
TypeScript | JavaScript | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
@Sugoi\core
We haven't tracked posts mentioning @Sugoi\core yet.
Tracking mentions began in Dec 2020.
node-config
-
topoconfig: enhancing config declarations with graphs
node-config
-
How We Converted a GitHub Tool Into a General Purpose Webhook Proxy to Supercharge Our Integration Development
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
Tailwind CSS v3.2.4 includes a new @config directive that lets you specify which Tailwind CSS config to use for that file.
-
Are env on vite process at runtime or buildtime?
Use https://www.npmjs.com/package/config so you can have runtime variables accessible based on provided json's
-
How to load config dynamically based on custom headers in monorepo?
I am using this node-config package (https://github.com/node-config/node-config) in my project. I feel like I am brute-forcing my way, is there a better way to do this? Any hint would be appreciated or just point me in a direction that would be great. Thank you!
- confuse.js
-
Managing Your Distributed Node.js Application Environment and Configuration
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.
-
I'm overcomplicating ENV, help
#3 Environment-specific config files with Config package
-
NextJS - Get rid of DotENV
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?
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?
What are some alternatives?
cluster-map - Abstracts execution of tasks in parallel using Node.js cluster.
cross-env
Commit-message - Holder of multiple npm packages
viper - Go configuration with fangs
Nuxt.js - Nuxt is an intuitive and extendable way to create type-safe, performant and production-grade full-stack web apps and websites with Vue 3. [Moved to: https://github.com/nuxt/nuxt]
configstore - Easily load and persist config without having to think about where and how
node-object-hash - Node.js object hash library with properties/arrays sorting to provide constant hashes. It also provides a method that returns sorted object strings that can be used for object comparison without hashes.
yargs - yargs the modern, pirate-themed successor to optimist.
Rambdax - Extended version of Rambda
chalk - 🖍 Terminal string styling done right
unleash - Open-source feature management solution built for developers.
log-symbols - Colored symbols for various log levels