deps: upgrade JSONStream@0.8 to jsonstream@1 #53
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There are a lot of problems with JSONStream vs. jsonstream due to case-folding and case-insensitive filesystems and how npm's cache works. The best way forward is for everyone to standardize on jsonstream, which is the canonical name for the module formerly called JSONStream.
|
For some relevant light reading, see dominictarr/JSONStream#68 and browserify/browserify#1247 |
tedeh
added a commit
that referenced
this pull request
Jun 4, 2015
deps: upgrade JSONStream@0.8 to jsonstream@1
|
Thanks! |
|
@tedeh from a quick look at v1.2.0...master it looks like there haven't been any changes that should be breaking.. Any chance of a minor release, assuming the TLS support is ready? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are a lot of problems with JSONStream vs. jsonstream due to
case-folding and case-insensitive filesystems and how npm's cache
works. The best way forward is for everyone to standardize on
jsonstream, which is the canonical name for the module formerly called
JSONStream.
Replacement for #52