Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

package-config

Package Overview
Dependencies
Maintainers
1
Versions
2
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

package-config

Get namespaced config from the closest package.json

  • 5.0.0
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
62K
decreased by-25.01%
Maintainers
1
Weekly downloads
 
Created
Source

package-config

Get namespaced config from the closest package.json

Having tool specific config in package.json reduces the amount of metafiles in your repo (there are usually a lot!) and makes the config obvious compared to hidden dotfiles like .eslintrc, which can end up causing confusion. XO, for example, uses the xo namespace in package.json, and ESLint uses eslintConfig. Many more tools supports this, like AVA, Babel, nyc, etc.

Install

npm install package-config

Usage

{
	"name": "some-package",
	"version": "1.0.0",
	"unicorn": {
		"rainbow": true
	}
}
import {packageConfig} from 'package-config';

const config = await packageConfig('unicorn');

console.log(config.rainbow);
//=> true

API

It walks up parent directories until a package.json can be found, reads it, and returns the user specified namespace or an empty object if not found.

packageConfig(namespace, options?)

Returns a Promise for the config.

packageConfigSync(namespace, options?)

Returns the config.

namespace

Type: string

The package.json namespace you want.

options

Type: object

cwd

Type: string
Default: process.cwd()

The directory to start looking up for a package.json file.

defaults

Type: object

The default config.

skipOnFalse

Type: boolean
Default: false

Skip package.json files that have the namespaced config explicitly set to false.

Continues searching upwards until the next package.json file is reached. This can be useful when you need to support the ability for users to have nested package.json files, but only read from the root one, like in the case of electron-builder where you have one package.json file for the app and one top-level for development.

Example usage for the user:

{
	"name": "some-package",
	"version": "1.0.0",
	"unicorn": false
}

packageJsonPath(config)

Pass in the config returned from any of the above methods.

Returns the file path to the package.json file or undefined if not found.

  • read-package-up - Read the closest package.json file
  • read-pkg - Read a package.json file
  • find-up - Find a file by walking up parent directories

Keywords

FAQs

Package last updated on 05 Nov 2023

Did you know?

Socket

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.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc