Skip to content

Commit

Permalink
Update deps to avoid jsonstream npm case problems
Browse files Browse the repository at this point in the history
See #1247
  • Loading branch information
zertosh committed May 7, 2015
1 parent b2284e1 commit 1ca71e2
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions package.json
Expand Up @@ -21,7 +21,7 @@
],
"dependencies": {
"assert": "~1.3.0",
"browser-pack": "^4.0.0",
"browser-pack": "^4.0.3",
"browser-resolve": "^1.7.1",
"browserify-zlib": "~0.1.2",
"buffer": "^3.0.0",
Expand All @@ -33,7 +33,7 @@
"crypto-browserify": "^3.0.0",
"deep-equal": "^1.0.0",
"defined": "^1.0.0",
"deps-sort": "^1.3.5",
"deps-sort": "^1.3.7",
"domain-browser": "~1.1.0",
"duplexer2": "~0.0.2",
"events": "~1.0.0",
Expand All @@ -43,11 +43,11 @@
"http-browserify": "^1.4.0",
"https-browserify": "~0.0.0",
"inherits": "~2.0.1",
"insert-module-globals": "^6.4.0",
"insert-module-globals": "^6.4.1",
"isarray": "0.0.1",
"jsonstream": "^1.0.3",
"labeled-stream-splicer": "^1.0.0",
"module-deps": "^3.7.7",
"module-deps": "^3.7.11",
"os-browserify": "~0.1.1",
"parents": "^1.0.1",
"path-browserify": "~0.0.0",
Expand Down

1 comment on commit 1ca71e2

@callumacrae
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It shouldn't be necessary, but you can't drop support for the latest couple versions of npm in a patch version without breaking semver.

Yes, it's caused by a bug in npm—but it was a change in browserify that caused the error to be thrown.

Please sign in to comment.