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

can-write

v0.1.1

Published

Test if a file or directory is writable

Downloads

12

Readme

can-write Build Status

Test if a file or directory is writable. Because sometimes you just gotta know.

Usage

var canWrite = require('can-write');

return canWrite('/path/to/my/file')
  .then(function(result) {
    if (result) {
      // writable
    } else {
      // not writable
    }
  }, function(err) {
    // some sort of error
  });
  
// alternatively:
  
canWrite('/path/to/my/file', function(err, result) {
  if (err) {
    // handle error 
  } else {
    if (result) {
    // writable
    } else {
      // not writable
    }
  }
});

Readability

Writability does not always imply readability. Think a "Drop Box", wherein guest users can put files in, but cannot read the contents.

To check readability, pass a truthy second parameter:

var canWrite = require('can-write');

return canWrite('/path/to/my/file', true)
  .then(function(result) {
    if (result) {
      // readable & writable
    } else {
      // either not readable or not writable.
      // if you need to know, call canWrite() again without the flag.
    }
  }, function(err) {
    // some sort of error
  });

Fair Warning

It's an anti-pattern to check writability.

You generally want to just do what you're going to do, then recover from an error.

For example, say you need to create a file:

fs.writeFile('/some/filepath', 'some data', function(err) {
  if (err.code === 'EACCESS') {
    // the file is not writable.
  }
});

In other words: don't use this module unless you really, really, really need to check whether something is writable.

Install

$ npm install can-write

License

© 2015 Christopher Hiller. Licensed MIT.