Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Jul 1, 2015
  1. @isaacs @iarna

    graceful-fs@4.1.2

    isaacs authored iarna committed
    PR-URL: #8735
Commits on May 8, 2015
  1. @isaacs @othiym23

    Upgrade to tap v1

    isaacs authored othiym23 committed
    node-tap v1.0.0 introduces a bunch of consistency and functionality
    upgrades in the test experience, along with a suite of pretty reporters
    ported from Mocha's default set.
    
    The semantic change that most dramatically affects npm's use (and will
    likely cause a bit of wailing and gnashing of teeth among other tap
    users) is that 't.test(...)' is now executed immediately, as long as
    there is not another test currently in progress.  Indeed, everything
    that the Test class does, it does right away at the moment of calling
    the function, never using nextTick to defer anything.
    
    This means that, for example, a 'console.log' in the middle of a bunch
    of tests will print its output in the context of the associated test
    output, instead of having the console.log happen first, and then all of
    the TAP data deferred until later.
    
    For new node-tap users, this has been a significant stumbling block.
    However, it is a breaking change, and requires that test fixture objects
    have to be set up in advance of being used by a test, since it's no
    longer a guarantee that everything at the top (module) level will be
    executed before any test blocks.
    
    Also, the statSync in config-meta was changed to an lstatSync, since I
    have been developing with tap link-installed, and the directory crawling
    was sending my system into a tailspin otherwise.  It seems like this
    would happen any time one of the npm deps was link-installed, so it's
    probably a good idea anyway.
Commits on Sep 30, 2014
  1. @isaacs

    bump npm-registry-couchapp dep

    isaacs authored
  2. @isaacs

    add readable-stream dedupe dep

    isaacs authored
  3. @isaacs
Commits on Sep 19, 2014
  1. @isaacs

    Add fs-write-stream-atomic dep

    isaacs authored
Commits on Sep 12, 2014
  1. @isaacs

    slide@1.1.6

    isaacs authored
Commits on Sep 11, 2014
  1. @isaacs

    semver@4.0.0

    isaacs authored
  2. @isaacs

    Remove engines

    isaacs authored
    Node v0.6 is pretty much gone at this point.  Also, the -pre upsets
    SemVer 4, making it annoying to test npm on Node in development.
  3. @isaacs

    s/ronn/marked-man/g

    isaacs authored
Commits on Sep 4, 2014
  1. @isaacs

    request@2.41.0

    isaacs authored
Commits on Aug 25, 2014
  1. @isaacs

    npmconf@2.0.6

    isaacs authored
Commits on Aug 22, 2014
  1. @isaacs

    package.json: Remove publishConfig

    isaacs authored
    Makefile already takes care of the correct tagging.
Commits on Aug 12, 2014
  1. @isaacs

    read-installed@3.1.0

    isaacs authored
Commits on Aug 1, 2014
  1. @isaacs

    read-installed@3.0.0

    isaacs authored
    Fixes extraneous peer dependent looping devDependencies in --production mode.
    
    CC @davglass
  2. @isaacs

    merge v1.4

    isaacs authored
Commits on Jul 31, 2014
  1. @isaacs

    v1.4.23

    isaacs authored
  2. @isaacs

    update several dependencies

    isaacs authored
    The quest to avoid SemVer '0.x' magic continues.
  3. @isaacs

    v1.4.22

    isaacs authored
  4. @isaacs

    read-package-json@1.2.4

    isaacs authored
  5. @isaacs

    github-url-from-git@1.2.0

    isaacs authored
  6. @isaacs

    fstream@0.1.29

    isaacs authored
  7. @isaacs

    glob@4.0.5

    isaacs authored
  8. @isaacs

    cmd-shim@1.1.2

    isaacs authored
Commits on Jul 30, 2014
  1. @isaacs

    init-package-json@1.0.0

    isaacs authored
    Defaults package versions in 'npm init' to 1.0.0 instead of 0.0.0
Commits on Jul 25, 2014
  1. @isaacs

    Bump semver to version 3

    isaacs authored
    This makes the '^' operator stricter for 0.x.y versions, even if 'x' is
    not 0.
    
    As a direct result, several *other* deps had to be updated, because they
    either depended on semver 2.x, or because the new stricter rules meant
    that they (or their deps) were no longer valid.
    
    The update to 'read-installed', in particular, causes a test failure.
    That update must be rolled back, or the test made to pass, prior to a
    stable npm 2.0.0 release going out.
Commits on Jul 23, 2014
  1. @isaacs

    npm-package-arg@2.0.1

    isaacs authored
Commits on Jul 18, 2014
  1. @isaacs

    upgrade npmconf and init-package-json

    isaacs authored
    Adds support for 'init.version' config, and falling back to _auth
    config as default auth when using default registry.
Commits on Jul 2, 2014
  1. @isaacs

    v1.4.20

    isaacs authored
Commits on Jul 1, 2014
  1. @isaacs

    v1.4.19

    isaacs authored
  2. @isaacs

    bump nopt and npmconf

    isaacs authored
    Fixes #5591
    
    The root cause here is that a change from 022 (a number in octal literal
    format) to '022' (a string) caused the string to later be interpreted as
    a decimal number, making for some wacky umask values.
    
    Solution is multipart.
    
    First, use the actual process.umask() value from the user's environment.
    This is almost certainly what they want anyway.
    
    Second, validate all default values just like we do with user- supplied
    values, rather than trusting them to never be wrong.  This would've
    found the problem much sooner, while in dev.
    
    This second part requires that we allow a value of null for 'path' type
    args, allow 'undefined' for the 'local-address' config, and avoid
    looking up a cafile of 'null', all of which are good hygenic things to
    add defense-in-depth anyway.
Commits on Jun 29, 2014
  1. @isaacs

    v1.4.18

    isaacs authored
  2. @isaacs

    glob@4.0.3

    isaacs authored
Commits on Jun 27, 2014
  1. @isaacs

    now working on v1.5.0

    isaacs authored
  2. @isaacs

    v1.4.17

    isaacs authored
Something went wrong with that request. Please try again.