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

@universal-packages/plugin-config-loader

v1.7.2

Published

Load your plugin configuration easily into a single plain old javascript object

Downloads

66,818

Readme

Plugin Config Loader

npm version Testing codecov

Load your plugin configuration easily into a single plain old javascript object, either if it has been provided in the package.json file or in some file named with your plugin's name.

Install

npm install @universal-packages/plugin-config-loader

Global methods

loadPluginConfig(pluginName: string, [options])

Reads deeply into files and directories named as the plugin name provided and get all the contents of the configuration files into a plain old javascript object.

import { loadPluginConfig } from '@universal-packages/plugin-config-loader'

const config = await loadPluginConfig('plugin')

console.log(config)

Loads all config files as json that matches the criteria in a conventional, files like:

 | package.json           <- First priority
   | "plugin": { ... }
 | plugin                 <- Forth priority
   | anything.json          <- 2
   | anything.yaml          <- loaded if not json
   | anything.[js|ts]       <- loaded if not yaml
 | .plugin                <- Fifth priority
   | anything.json          <- 2
   | anything.yaml          <- loaded if not json
   | anything.[js|ts]       <- loaded if not yaml
 | plugin.json            <- Second priority
 | plugin.yaml            <- loaded if not json
 | plugin.[js|ts]         <- loaded if not yaml
 | .plugin.json           <- Third priority
 | .plugin.yaml           <- loaded if not json
 | .plugin.[js|ts]        <- loaded if not yaml

You can always modify the priority of location and format in the options.

Options

  • cleanOrphanReplaceable boolean Replaceable strings that are not found in the environment variables will be removed from the final values.

  • defaultConfig Object Use to fill config that may not be present in the configuration files.

  • formatPriority ['json' | 'yaml' | 'yml' | 'js' | 'ts'] Prioritization order if one format is desired but does not exists which one try next?

  • loadFrom string By default it will try to load from the root path but a different path can be specified to load from.

  • locationPriority ['package' | 'root' | '.root' | 'directory' | '.directory'] By default is loaded from the package first but you can change the order of the location to be fetch first.

    • package: Internally embedded in the package.json file
    • root: A file named as the plugin name, ex: jest.js
    • .root: A file named as the plugin name with a prefixed dot, ex: .jest.js
    • directory: A folder containing more that one config file named as the plugin name, ex: ./github
    • .directory: A folder containing more that one config file named as the plugin name with a prefixed dot, ex: ./.github
  • selectEnvironment string | boolean If you want your files to be post processed after loaded with a selection of an environment section you can specify the name of the environment to select or pass true to automatically set from NODE_ENV.

Typescript

This library is developed in TypeScript and shipped fully typed.

Contributing

The development of this library happens in the open on GitHub, and we are grateful to the community for contributing bugfixes and improvements. Read below to learn how you can take part in improving this library.

License

MIT licensed.