Skip to content
Commits on Jun 1, 2015
Commits on May 14, 2015
  1. @substack

    0.5.1

    substack committed
  2. @substack

    update travis targets

    substack committed
Commits on May 13, 2015
  1. Remove octal literals, pass in strict mode

    committed
    We all hate this.  But since this module is used everywhere, it's
    a pain to not be able to use it in environments where strict mode
    is desired, even if that desire is misguided.
Commits on May 6, 2014
  1. @substack

    0.5.0

    substack committed
  2. @substack

    document opts.fs

    substack committed
  3. @substack
  4. @substack

    failing opts.fs sync test

    substack committed
  5. @substack
  6. @substack

    test suite cleanup

    substack committed
  7. @substack

    reformat package.json

    substack committed
  8. @substack
  9. @substack

    failing opts.fs test

    substack committed
  10. @substack

    0.4.2

    substack committed
  11. @sqs @substack
  12. @doublerebel @substack

    Parsing mode from string already in node's lib.js

    doublerebel committed with substack
    Hello,
    
    Node's fs.mkdir and fs.mkdirSync already call an internal modeNum method to parse the mode from string type.  Therefore it is unneeded in this lib.
    
    See: https://github.com/joyent/node/blob/master/lib/fs.js#L324
    
    Thanks!
    
    **Charles**
Commits on May 4, 2014
  1. @substack

    0.4.1

    substack committed
  2. @calvinmetcalf @substack

    add minimist

    calvinmetcalf committed with substack
Commits on Apr 22, 2014
  1. @substack

    swap 0.9 for 0.10 on travis

    substack committed
  2. @substack

    0.4.0

    substack committed
  3. @substack

    usage

    substack committed
  4. @substack

    --help

    substack committed
  5. @substack
  6. @calvinmetcalf @substack

    add cli

    calvinmetcalf committed with substack
Commits on Feb 22, 2013
  1. @substack

    drop 0.4, add 0.9

    substack committed
  2. @substack

    modernize readme, deps

    substack committed
Commits on Feb 12, 2013
  1. @ulikoehler
Commits on Aug 20, 2012
  1. @substack

    0.3.4

    substack committed
Commits on Jun 16, 2012
  1. All non-ENOENT errors should be handled the same

    committed
    There's a lot of special-casing for EISDIR, EEXIST, etc.  It dawned on me
    that we've special cased all the errors that fs.mkdir() can possibly raise,
    so why not just make that the default: case, and cut out a bunch of code
    that has to be read?
    
    Argument against: if some error is ever raised, which *isn't* an error that
    fs.mkdir() can 'possibly' raise, then it's raising an error that is *impossible*
    and we probably want to get out asap.
    
    But even in the case of impossible errors, if the dir is there, and it's
    a dir, then who cares?  mkdir(1) ignores any errors making a directory with
    -p if the directory exists and is a directory.
Commits on Jun 5, 2012
  1. @substack
Commits on Jun 4, 2012
Commits on May 23, 2012
  1. @substack
Commits on Apr 30, 2012
  1. @substack

    bump for erofs

    substack committed
Commits on Apr 16, 2012
  1. Handle EROFS errors

    committed
    A EROFS will be raised when trying to write a dir onto a
    read-only filesystem.  However, if the dir already is there,
    then it should be treated like an EEXIST (since EROFS can
    be raised by trying to create a dir over a mount point,
    where the mount point is not read-only, but you still can't
    just clobber over it).
    
    If the dir doesn't already exist, then the EROFS will be
    accurately reported as the reason why it could not be
    created.
Something went wrong with that request. Please try again.