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

@technician/source-fs

v2.0.1

Published

Access config on your local filesystem with Technician.

Downloads

6

Readme

@technician/source-fs

npm version npm downloads npm license

dependencies Build Status GitKraken

A config source for accessing config stored on the filesystem, allowing access to several config files stored in the same directory. It useable as both an async and sync config source.

This package provides the FSConfigSource for use with the Technician manager.

Technician

Installation

npm i @technician/source-fs

This package is compatible with Node 10 LTS and up.

Usage Examples

FSConfigSource returns Buffer data by default and uses filenames as keys.

The Basics

import {Technician} from 'technician';
import {FSConfigSource} from '@technician/source-fs'

const technician = new Technician(new FSConfigSource());

// By default, FSConfigSource reads from process.cwd();
await technician.read('.myapprc');
await technician.read('something-else.json');

Working With JSON

import {Technician, Interpret} from 'technician';
import {FSConfigSource} from '@technician/source-fs'

const technician = new Technician(Interpret.buffer.asJSON(new FSConfigSource(), 'utf8'));
const config = await technician.read('config.json');

// The default asJSON interpreter can read and return JSON files as a js object.
// Non-JSON will be ignored with `asJSON`.
// You can use `asStringOrJSON` to parse JSON only when valid and otherwise return strings.
db.connect(config.dbUsername, config.dbPassword);

Specifying Directories

// Provide an absolute path to a directory.
new FSConfigSource('/home/me/my-config-dir');

// The relativeRootPath option will look inside process.cwd() for your custom path.
new FSConfigSource('app-config-dir', {relativeRootPath: true});

Recursive Reading

// Recursively reads subdirectories.
technician.addSource(new FSConfigSource(), {recurse: true});

// Read a file at the top level...
await technician.read('top-level-file.txt');
// ... or within nested subdirectories
await technician.read('subdirectory/another-file.txt');

// Subdirectories are not expanded into objects with readAll(),
// but instead keep the same flat key structure used by read().
// Ex: {"top-level-file.txt": "contents", "subdirectory/another-file.txt": "contents"}

Errors

By default, the FSConfigSource suppresses all filesystem errors (except in the case that the rootPath passed to the constructor is invalid), instead treating any unreadable files as simply nonexistent.

To throw these errors instead, use the {throwErrors: true} option. Note that this will cause readAll() to throw an error if the target directory contains any inaccessible files, even if others are valid.

Contributions

Contributions and pull requests are always welcome. Please be sure your code passes all existing tests and linting.

Pull requests with full code coverage are strongly encouraged.

License

Apache-2.0