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

@meniga/config

v6.1.37-alpha.0

Published

A library that gives access to config files in Meniga apps

Downloads

573

Readme

@meniga/config

Config is a utility library that reads the cosmicConfig property from the window object and merges in a built config object.

@meniga/cli can help create these configs for different environments. See here.

Exports


globalConfig

globalConfig is a wrapper for Config.get, and can be used like this:

const someValue = globalConfig('path/to/config', someDefaultValue)

Example:

import { globalConfig } from '@meniga/config'

const _configItemsPerPage = globalConfig('transactions.itemsPerPage', 50)

getBooleanConfigValue

getBooleanConfigValue makes sure that the value you get from the config is a boolean (e.g. if the config file itself has a string value 'true' you will get back a Boolean(true)). Example:

import { getBooleanConfigValue } from '@meniga/config'

const _configShowCurrentMonthInChart = getBooleanConfigValue('transactions.showCurrentMonthInChart', false)

getIntConfigValue

getIntConfigValue makes sure that the value you get from the config is an integer (e.g. if the config file itself has a string value '10' you will get a Number(10) back). Example:

import { getIntConfigValue } from '@meniga/config'

const _configUndoCategoryChangeTimeout = getIntConfigValue('transactions.undoCategoryChangeTimeout', 3000)

default

The default export is the config class. This class has 4 methods:

  • get(key, defaultValue = null) : gets the vale from the merged config, if null then returns the default value

  • all() : get the whole merged config object

  • pretty() : prints the merged config object out to the console

  • init() : initializes @meniga/config by preloading JSON config files (config/config.json and config/override.json) generated by webpack and exposes them to the get(), all() and pretty() methods. This method should be called during the initialization of your app.

  • load(cosmicJsonConfig, overrideJsonConfig) : Initialize @meniga/config by setting already fetched JSON config files generated by webpack and assigning them to the "window.cosmicConfig" and "window.cosmicOverride" javascript variables.