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

vscode-config-resolver

v1.0.3

Published

Find configuration for the current file from provided path, workspace, package or HOME directory

Downloads

3

Readme

vscode-config-resolver

Find configuration for the current file from provided path, workspace, package or HOME directory.

Donate

If you want to thank me, or promote your Issue.

Gratipay User

Sorry, but I have work and support for plugins requires some time after work. I will be glad of your support.

Install

$ npm i -S vscode-config-resolver

Why?

  • Because many plugins use similar code.
  • To simplify work with the configs in plugins.

Usage

const ConfigResolver = require('vscode-config-resolver');

const configResolver = new ConfigResolver('./path/to/workspace/');

configResolver.scan('./path/to/current/file', {}).then((config) => {
  console.log(config);
  // { from: '', json: {} }
});

API

.scan(filepath, [options])

Find configuration for the current file.

options

packageProp

  • Type: String
  • Default: null

The property that contains the configuration. Automatically adds the package.json file to options.configFiles.

configFiles

  • Type: String[]
  • Default: []

An array of files that may contain configuration.

editorSettings

  • Type: Object or String
  • Default: null

Config from editor preferences. Supports:

  • Path with ~
  • Path with . or ../ or /
  • Object
  • Name of predefined config

predefinedConfigs

  • Type: Object
  • Default: {}

If options.editorSettings contains the name of configuration.

parsers

  • Type: IParser[]
  • Default: js + json
[
  { pattern: /.*(json|rc)$/, parser: JSON.parse },
  { pattern: /.*(js|rc)$/, parser: requireString }
]

Changelog

See the Releases section of our GitHub project for changelogs for each release version.

License

This software is released under the terms of the MIT license.