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

@shons/next-configify

v1.0.1

Published

NestJS Config on Next Steroids

Downloads

3

Readme

Next-Description

next-configify is just a small extension to the existing @itgorillaz/configify project with following features which I needed in my own project.

  1. environment profile (dev, prod, stage, test) based configuration files loading
  2. register configuration properties as environment variables e.g. app.my.property --> APP_MY_PROPERTY or app.my-property.default --> APP_MY_PROPERTY_DEFAULT
  3. If duplicate properties are found, lateral ones will be considered
  4. Environement properties will always take precedence
  5. if all config type files are provided then precedence would be as follows: application.yml -> application.yaml -> application.json -> .env -> customprops.[yml|json|.env] --> environemntVariables when envProfile is set application.yml -> application.yaml -> application.json -> .env -> application-<envProfile>.yml -> application-<envProfile>.yaml -> application-<envProfile>.json -> .<envProfile>.env -> customprops.[yml|json|.env] --> environemntVariables

How to set 'environment profile'?

You can add module otions by providing an object as argumento to the forRootAsync() method:

/**
   * then environment name to load environemnt specific file.
   * 
   *  e.g. if envProfile: 'prod';  ```applicaition-prod.yml or application-prod.json or .prod.env``` files will be loaded in addition to default files
   */
  envProfile?: string
  
  

for rest of the Readme please go @it-gorillaz/configify

License

This code is licensed under the MIT License.

All files located in the node_modules and external directories are externally maintained libraries used by this software which have their own licenses; we recommend you read them, as their terms may differ from the terms in the MIT License.