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

fsq

v1.0.3

Published

Node.js FS with Q.js

Downloads

12

Readme

fsq Build Status NPM version

Node.js FS with Q.js

Installation

npm install fsq

Discussion

####What?

This module takes Node.js (v0.10.x) FS module, promisify's all its functions using Q.js, and gives them back to you. It also queues all your requests to avoid the EMFILE error.

####Why?

I like Promises.

####Anything else?

Well yes, seeing as you asked. You can quite often run into the EMFILE error whereby you have too many file descriptors open. The "fix" is usually to allow more file descriptors, but that seems to be just delaying the inevitable.

Since we are doing asynchronous IO anyway, it shouldn't really matter if we take a slightly more pragmatic approach and queue up our FS requests when we start hitting the EMFILE limit.

graceful-fs does this, but I think it only queues open() and readdir(), and doesn't use Promises. I like Promises.

API

In terms of parameters, all the asynchronous Node.js FS functions are reproduced as-is, according to the documentation at time of writing.

The exceptions here are that the callback parameter should not be passed (it will be ignored), and all functions return a Promise, which, as it is generated by Q, will only supply one value when resolved. This value will be an Object, with its keys matching the names of the return parameters for the associated FS functions.

#####fsq.readFile(filename, [options]) See fs.readFile for parameter details.

Promise resolves with Object:

  • data (String if encoding is specified in options, otherwise Buffer)

#####fsq.writeFile(filename, data, [options]) See fs.writeFile for parameter details.

Promise resolves with undefined.

#####fsq.exists(path) See fs.exists for parameter details.

Promise resolves with Object:

  • exists (Boolean)

#####fsq.readdir(path) See fs.readdir for parameter details.

Promise resolves with Object:

  • files (Array)

Examples

######writeFile example.

var fsq = require("fsq");

fsq.writeFile("world.json", "Hello").then(
	function () {
		console.log("writeFile success!");
	},
	function (err) {
		console.log("writeFile error: " + err);
	}
);

Bitdeli Badge