Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master
Commits on Apr 21, 2015
  1. @othiym23

    editor@1.0.0

    othiym23 authored
    1.0.0 is bigger than 0.1.0. (@substack)
  2. @othiym23

    npm-registry-client@6.3.3

    othiym23 authored
    * When the registry returns a scoped package name in error messages,
      renormalize it back out of URLEncoded format. (@mmalecki)
    * Clean up the `npm:` example in the README. (@evilpacket)
Commits on Apr 17, 2015
  1. @othiym23

    update AUTHORS

    othiym23 authored
  2. @othiym23

    2.8.4

    othiym23 authored
  3. @othiym23

    update changelog for 2.8.4

    othiym23 authored
  4. @othiym23

    tar@2.1.0

    othiym23 authored
    * properly error on malformed tar files
    * use fromBase property to set extraction root
  5. @zeke @othiym23

    six was not a useful number

    zeke authored othiym23 committed
    and maybe it wasn't even the right number?
  6. @sandfox @othiym23

    Make npm init text a little more friendly

    sandfox authored othiym23 committed
    I'm not sure we should use the word "sane" to refer settings etc, it seems a little ableist and there are are nicer and more accurate words we could use instead.
  7. @othiym23

    lru-cache@2.6.1

    othiym23 authored
    * more tweaks to maxAge behavior
    * length and itemCount added to gauge number of items in cache
  8. @othiym23

    init-package-json@1.4.1

    othiym23 authored
    * set a default (empty) value for the author field to make `npm init -y`
      work without user input
    * allow at most one scope on a package name, replacing the new scope if
      an existing one is available
Commits on Apr 16, 2015
  1. @othiym23

    2.8.3

    othiym23 authored
  2. @othiym23
  3. @othiym23

    git: git: -> https: -> ssh:

    othiym23 authored
    Swapped SSH and HTTPS URLs to make the error messaging make more sense,
    and also make it less common for users to be stuck with password prompts
    they can't do anything about.
  4. @othiym23
Commits on Apr 15, 2015
  1. @othiym23
  2. @othiym23

    2.8.2

    othiym23 authored
  3. @othiym23
Commits on Apr 14, 2015
  1. @othiym23

    npm-registry-client@6.3.2

    othiym23 authored
    Don't send body with HTTP GET requests, which confuses the keep-alive
    agent and triggers all kind of weird behavior. Fixes #7699. All glory to
    smikes for finding and fixing this issue.
Commits on Apr 13, 2015
  1. @othiym23

    2.8.1

    othiym23 authored
  2. @othiym23

    update AUTHORS

    othiym23 authored
  3. @othiym23
  4. @othiym23

    lru-cache@2.5.2

    othiym23 authored
    More accurate updating of last access time when `maxAge` is set.
  5. @othiym23

    test: eliminate fixture directories from test/tap

    othiym23 authored
    It's too difficult for npm contributors to figure out what the
    conventional style is for tests. Part of the problem is that the
    documentation in CONTRIBUTING.md is inadequate, but another important
    factor is that the tests themselves are written in a variety of styles.
    One of the most notable examples of this is the fact that many tests use
    fixture directories to store precooked test scenarios and package.json
    files.
    
    This had some negative consequences:
    
      * tests weren't idempotent
      * subtle dependencies between tests existed
      * new tests get written in this deprecated style because it's not
        obvious that the style is out of favor
      * it's hard to figure out why a lot of those directories existed,
        because they served a variety of purposes, so it was difficult to
        tell when it was safe to remove them
    
    All in all, the fixture directories were a major source of technical
    debt, and cleaning them up, while time-consuming, makes the whole test
    suite much more approachable, and makes it more likely that new tests
    written by outside contributors will follow a conventional style. To
    support that, all of the tests touched by this changed were cleaned up
    to pass the `standard` style checker.
  6. @othiym23

    test: move fixtures from test/tap to test/fixtures

    othiym23 authored
    Some fixtures are necessary, but they should all be combined into one
    place to signpost what they're for.
    
    Part of #7929.
  7. @othiym23
  8. @robertkowalski @othiym23

    remove child-process-close

    robertkowalski authored othiym23 committed
    npm doesn't support Node 0.6 any more.
Commits on Apr 11, 2015
  1. @watilde
  2. @watilde
  3. @othiym23
  4. @othiym23
  5. @ewie @othiym23

    install: scoped packages with peerDependencies

    ewie authored othiym23 committed
    Package scopes cause an additional level in the tree structure which
    must be considered when resolving the target folders of a package's
    peerDependencies.
    
    Fixes #7454.
  6. @othiym23
  7. @othiym23

    hosted-git-info@2.1.2

    othiym23 authored
    `git+https:` and `git+http:` are authed protocols.
Commits on Apr 10, 2015
  1. @othiym23

    nock@1.6.0

    othiym23 authored
  2. @othiym23

    glob@5.0.5

    othiym23 authored
    Move platform-specific shim from one place to another.
Something went wrong with that request. Please try again.