Security News
tea.xyz Spam Plagues npm and RubyGems Package Registries
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
@qte/nest-config
Advanced tools
A module for advanced configurations in Nest, supporting YAML, Env values, and Google Secret Manager secrets. The module aims to provide flexibility, while also providing a great deal of safety. One of the guiding principles is to fail fast. The module wi
Readme
A module for advanced configurations in Nest, supporting YAML, Env values, and Google Secret Manager secrets. The module aims to provide flexibility, while also providing a great deal of safety. One of the guiding principles is to fail fast. The module will throw early errors crashing the application if anything goes wrong.
$ yarn add @qte/nest-config
Note that zod
is a peer-dependency and must be installed separately.
Import and configure the module in the following way
import { ConfigModule, ConfigService, DEVELOPMENT } from '@qte/nest-config'
import { z } from 'zod'
const mySchema = z.object({
port: z.number()
}).strict()
type Config = z.infer<typeof mySchema>
// The module is global
ConfigModule.forRoot({
env: DEVELOPMENT,
schema: mySchema,
configPath: './config' // Optional argument, defaults to the ./config directory relative to the running node process
})
// Later on in any other Nest provider or controller
const myConfig = ConfigService.getConfig<Config>()
You must create the following files
touch ./config/index.yaml # This is your base configuration
touch ./config/env.development.yaml # This file is loaded if env is DEVELOPMENT
touch ./config/env.staging.yaml # This file is loaded if env is STAGING
touch ./config/env.production.yaml # This file is loaded if env is PRODUCTION
The final configuration is built from first parsing index.yaml
, then merging it with the environment specific configuration.
Duplicate object keys are merged recursively, while all other duplicates are overriden, and the environment configuration is prioritised.
# index.yaml
database:
user: postgres
password: development
# env.production.yaml
database:
password: super-secret-prod-password # Ideally read from a secret
Merges to
const config = {
database: {
user: 'postgres',
password: 'super-secret-prod-password',
}
}
Configuration files can contain ENV
values and Google Secrets Manager secrets. See examples below
database:
host:
$from:
env: DATABASE_ENV # Will read PROCESS.ENV.DATABASE_ENV
password:
$from:
secret: projects/some-gcp-project/secrets/some-secret/versions/latest # Will read the secret from GCP
the parsed configuration will match the following schema
z.object({
database: z.object({
host: z.string(),
password: z.string(),
}),
})
The package caches secrets in development mode. Clear the cache by running
rm -rf $TMPDIR/nest-config
You can also disable caching by setting cache: false
in the module options
@qte/nest-config is MIT licensed.
FAQs
A module for advanced configurations in Nest, supporting YAML, Env values, and Google Secret Manager secrets. The module aims to provide flexibility, while also providing a great deal of safety. One of the guiding principles is to fail fast. The module wi
The npm package @qte/nest-config receives a total of 72 weekly downloads. As such, @qte/nest-config popularity was classified as not popular.
We found that @qte/nest-config demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
Security News
As cyber threats become more autonomous, AI-powered defenses are crucial for businesses to stay ahead of attackers who can exploit software vulnerabilities at scale.
Security News
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.