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

utils-fs-exists

v1.0.1

Published

Tests whether a path exists on the filesystem.

Downloads

27

Readme

Exists

NPM version Build Status Coverage Status Dependencies

Tests whether a path exists on the filesystem.

Installation

$ npm install utils-fs-exists

Usage

var exists = require( 'utils-fs-exists' );

exists( path, clbk )

Tests whether a path exists on the filesystem.

exists( __dirname, done );

function done( bool ) {
	if ( bool ) {
		console.log( '...path exists.' );
	} else {
		console.log( '...path does not exist.' );
	}
}

The above callback signature matches the now deprecated fs.exists() API. The function also accepts the more conventional error-first style callback signature found in most asynchronous Node APIs.

exists( __dirname, done );

function done( error, bool ) {
	if ( error ) {
		console.error( error );
	}
	if ( bool ) {
		console.log( '...path exists.' );
	} else {
		console.log( '...path does not exist.' );
	}
}

exists.sync( path )

Synchronously tests whether a path exists on the fileystem.

var bool = exists.sync( __dirname );
// returns <boolean>

Notes

  • The following is considered an anti-pattern:

    var fs = require( 'fs' ),
    	path = require( 'path' );
    
    var file = path.join( __dirname, 'foo.js' );
    if ( exists.sync( __dirname ) ) {
    	file = fs.readFileSync( file );
    }

    Because time elapses between checking for existence and performing IO, at the time IO is performed, the path can no longer be guaranteed to exist. In other words, here, a race condition exists between the process attempting to read and another process attempting to delete.

    Instead, the following pattern is preferred, where errors are handled explicitly:

    var fs = require( 'fs' ),
    	path = require( 'path' );
    
    var file = path.join( __dirname, 'foo.js' );
    try {
    	file = fs.readFileSync( file );
    } catch ( error ) {
    	console.log( 'unable to read file.' );
    	console.error( error );
    }
  • Nevertheless, use cases exist where one desires to check existence without performing IO. For example,

    var fs = require( 'fs' ),
    	path = require( 'path' );
    
    var file = path.join( __dirname, 'foo.js' );
    if ( exists.sync( file ) ) {
    	console.log( 'Don\'t overwrite the file!' );
    } else {
    	fs.writeFileSync( file, 'beep', {
    		'encoding': 'utf8'
    	});
    }

Examples

var exists = require( 'utils-fs-exists' );

// Sync:
console.log( exists.sync( __dirname ) );
// returns true

console.log( exists.sync( 'beepboop' ) );
// returns false


// Async:
exists( __dirname, done );
exists( 'beepboop', done );

function done( error, bool ) {
	if ( error ) {
		console.error( error.message );
	} else {
		console.log( bool );
	}
}

To run the example code from the top-level application directory,

$ node ./examples/index.js

Tests

Unit

Unit tests use the Mocha test framework with Chai assertions. To run the tests, execute the following command in the top-level application directory:

$ make test

All new feature development should have corresponding unit tests to validate correct functionality.

Test Coverage

This repository uses Istanbul as its code coverage tool. To generate a test coverage report, execute the following command in the top-level application directory:

$ make test-cov

Istanbul creates a ./reports/coverage directory. To access an HTML version of the report,

$ make view-cov

License

MIT license.

Copyright

Copyright © 2015. Athan Reines.