Permalink
Commits on Mar 7, 2017
  1. 1.0.11

    zkat committed Mar 7, 2017
  2. Move props.path check below class init (#55)

    ZJONSSON committed with zkat Mar 7, 2017
    `self.error` is not available until the prototype is available
    
    PR-URL: #55
    Credit: @ZJONSSON 
    Reviewed-By: @zkat
Commits on Jun 17, 2016
  1. build: clean up versions

    othiym23 committed Jun 17, 2016
    Also quote the version numbers, so Travis doesn't try to test fstream
    against Node 0.1.
  2. 1.0.10

    othiym23 committed Jun 17, 2016
  3. collect: respect stream pause / resume state

    rvagg committed with othiym23 Jun 17, 2016
    Without watching if a stream is already paused before calling pause(),
    collect() can conflict with other users of the stream who may be
    managing state, resulting in a premature collect().  This manifests in
    the fstream-npm and node-tar combination where fstream-npm manages state
    in readBundledLinks() at the same time collect() is processing the
    stream. collect() ends up running before fstream-npm has properly set up
    the _correct_ list of entries according to the ignore rules. When
    collect() gets to run before this is complete, fstream starts performing
    _read() operations on a non-filtered list, keeping track of entry index,
    then after it starts, fstream-npm inserts a new list of entries and the
    entry index is incorrect and can skip files.
    
    Fixes: npm/npm#5082
    Credit: @rvagg
    Reviewed-By: @othiym23
    PR-URL: #53
  4. dir-reader: revert a55ae72

    rvagg committed with othiym23 Jun 17, 2016
    Unnecessary when collect() handles pause/resume state properly, this
    compounds the issue and adds unnecessary entries to the list.
    
    Credit: @rvagg
    Reviewed-By: @othiym23
    PR-URL: #53
Commits on May 12, 2016
  1. 1.0.9

    othiym23 committed May 12, 2016
  2. read: account for entries changed after _read

    evanlucas committed with othiym23 Apr 28, 2016
    If this.entries is changed after _read() has been called, we will be
    out of sync and try to access an invalid index of this.entries. When
    the entry cannot be found, we emit end and close, which can drop files
    from reading.
    
    (At least partially) fixes npm/npm#5082.
    
    Credit: @evanlucas
    Reviewed-By: @othiym23
    PR-URL: #50
Commits on Oct 8, 2015
  1. package: fix repository link

    iarna committed Oct 8, 2015
Commits on Sep 10, 2015
  1. 1.0.8

    zkat committed Sep 10, 2015
  2. deps: Upgrade graceful-fs dependency to the latest

    thefourtheye committed with zkat Sep 6, 2015
    graceful-fs used to monkey-patch node's core fs module.
    This has been fixed in the version 4.
    
    PR-URL: #45
Commits on Jun 19, 2015
  1. 1.0.7

    othiym23 committed Jun 19, 2015
Commits on Jun 5, 2015
  1. standard@4.0.0 and tap@1.2.0

    isaacs committed Jun 1, 2015
Commits on May 8, 2015
  1. 1.0.6

    iarna committed May 8, 2015
  2. Revert "package: Fix incorrect version specifier for mkdirp"

    iarna committed May 8, 2015
    This reverts commit c16d373.
    
    The original commit changed ^0.5.0 to >=0.5 0
    
    And it turns out that despite A) making the versions travis was configured
    to work with explode and B) looking wrong, it is, in fact, correct.
    
    What it's saying is >=0.5 AND a major version of 0. Which is what we'd
    probably want. Though it's interesting to note that it's not semantically
    equivalent to ^0.5.0. ¯\_(ツ)_/¯
  3. reader: undo setting of default reader class as ProxyReader

    iarna committed May 8, 2015
    Specifically, when the Reader constructor call is determining what
    class to construct it selects a default class of Reader or whatever
    was explicitly passed into it.
    
    If it was a "type" as a string the the look for that will override
    the previous type.
    
    When the file was being reformatted for standardization it got a
    default added to the type string-based look up. This resulted in
    any non string-based type being constructed as a ProxyReader type,
    instead of the custom type that was selected.
    
    As npm uses custom fstream readers, this resulted in npm and its
    tests exploding.
  4. 1.0.5

    othiym23 committed May 8, 2015
Commits on Mar 7, 2015
  1. standard

    feross committed with othiym23 Feb 19, 2015
Commits on Feb 9, 2015
Commits on Feb 4, 2015
  1. make fstream standard

    othiym23 committed Feb 4, 2015
    * depend on http://npm.im/standard
    * copy standard's .eslintrc to root for use by editors running eslint
    * add `standard &&` to `npm test`
    * reformat everything to pass standard's style checks
    
    The only oddity here is that since `standard` is set to check for both
    Node and browser compliance, some variables at the module scope level
    (`closed`, `FileReader`) are marked as read-only. See discussion on
    eslint/eslint#892 for details.
Commits on Feb 3, 2015
  1. rm unused fs, fstream

    coderaiser committed with othiym23 Dec 4, 2014
Commits on Jan 24, 2015
  1. 1.0.4

    othiym23 committed Jan 24, 2015
Commits on Jan 15, 2015
Commits on Nov 28, 2014
  1. 1.0.3

    othiym23 committed Nov 28, 2014
Commits on Nov 26, 2014
Commits on Nov 24, 2014