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

pub-src-fs

v2.2.0

Published

Default file system source for pub-server and pub-generator

Downloads

77

Readme

pub-src-fs

CI

Default file system source for pub-server and pub-generator

  • provides get() and put() for bulk reads and writes
  • globs and descends directories
  • assumes that all files with non-binary extensions are utf-8 text

src(options)

var src = require('pub-src-fs');

// instantiate source on path
// options become properties of source
var source = src( { path:'.', glob:'**/*.js', depth:2, writable:true } );

source.get(function(err, files) {
  if (err) return console.log(err);
  console.log(_.pluck(files, 'path'));
});

source.path

  • recurses directories starting with path
  • omits any directories starting with '.'
  • results will not include the path, just a /

source.glob

  • glob is a node-glob pattern
  • in order to support recursive descent on other systems (like github) this implementation does not use the glob library to walk directories
  • instead it walks directories and then calls minimatch to test the files in those directories.
  • because path is used as the root for globbing, globstars in the middle of the pattern are unlikely

source.depth

  • depth limits the depth of tree traversal when there is globstar
  • this is useful for avoiding symlink cycles and improving performance

source.writable

  • required true for successful .put()

source.writeOnly

  • disables reading with .get()

source.dirsFirst

  • if dirsFirst is true, entries within each directory will be returned with directories before files instead of the default (files first)

source.dirsSame

  • if dirsSame is true, directories and files sort together (overrides dirsFirst)

source.get(cb)

  • get() fetches all matching files in one async operation
  • the result is an array of file objects each with a path: and a text: property (for non-binary files), or a buffer: property (for binary files)
  • the array is sorted alphabetically by path
  • results do not include directories, but do include files in subdirectories
  • if the source is writable, get() is atomic with respect to put() or other source.get() operations
[ { path: '/fs-base.js',
    text: '...' },
  { path: '/pub-src-fs.js',
    text: '...' } ]

source.put(files, cb)

  • put() does nothing unless writable is set on the source
  • it writes an array of file objects back to the file system overwriting existing files
  • there is no partial file write but the array may contain a subset of the files read via get()
  • put() is atomic with respect to source.get() or other source.put() operations
  • put() tries to avoid file corruption by writing to a temp location and then renaming files
  • put() returns an array of the paths written
source.put(files, function(err, result) {
  if (err) return console.log(err);
  console.log(result);
});