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 🙏

© 2026 – Pkg Stats / Ryan Hefner

cfs

v0.6.0

Published

Conditional file streams

Downloads

13

Readme

Node.js: conditional file streams

build status windows Build status Coverage Status

Writable file stream that can write to different files based upon the condition of what's being written. i.e. Intead of passing filePath as the first parameter to your stream, you pass a function that returns the path.

This saves you time because you no longer have to manage many different writable streams.

Use Case

Best use case is to only have one writable fs stream that writes log files, except the log file path changes depending up the date or log data.

Usage

npm i --save cfs

Example 1

Write log data to different files depending upon the date.

var cfs = require('cfs')
var path = require('path')
var ymd = require('ymd')

var pathFn = function () {
  // get date in YYYY-MM-dd
  var date = ymd(new Date())
  return path.join('/tmp/logs/' + date + '.txt')
}

var logWriter = cfs.createWriteStream(pathFn, { flags: 'a' })
logWriter.write(someLogData)

Example 2

Write data to different files depending upon what's being written. Write even numbers to evens.txt and odd numbers to odds.txt.

No need to worry about opening a bunch of files. File descriptors are cached.

var cfs = require('cfs')

var pathFn = function (data) {
  if (data == null) return null

  if (parseInt(data.toString('utf8'), 10) % 2 === 0) {
    return 'evens.txt'
  } else {
    return 'odds.txt'
  }
}

var logWriter = cfs.createWriteStream(pathFn, { flags: 'a' })
logWriter.write(someLogData)

API

createWriteStream()

  • pathFunction: A function that should return the path. Method signature (data, encoding).
  • options: These are the standard options that you'd pass to fs.createWriteStream. Also, cacheOptions which are the options that you'd pass to lru-cache.

License

MIT

Copyright (c) JP Richardson