jsonparse

This project publishes no release notes. Between 1.3.0 and 1.3.1 there were 3 commits, 1 of them substantive:

• Allow parse escaped surrogate pairs

This project publishes no release notes. Between 1.2.0 and 1.3.0 there were 7 commits, 5 of them substantive:

• don't oom on long strings
• make tests work on old versions of node
• add char code constants
• cleanup buffer copy size logic
• Merge tag '1.2.0'

This project publishes no release notes. Between v1.0.0 and 1.2.0 there were 20 commits, 16 of them substantive:

• Fix prototype issue
• Upgrade patch version number
• Implement toknam as a private static method
• Refactoring
• Fix ending of parsing when an error is encountered
• Fix ending of parsing when an error is encountered (second pass)
• Add STOP state, used to implements a panic state recovery mechanism.
• Bump the middle number version
• Add unitary test
• Refacrotored number parsing with parseFloat
• Unit tests are passing after refactoring
• Error handling just like the rest of the code
• Overflow check
• Overflow check, passing a string
• Fix infinite loop for characters above 244
• Added few tests for the long numbers and improved the check

This project publishes no release notes. Between 0.0.6 and v1.0.0 there were 5 commits, 3 of them substantive:

• remove second definition of proto.onError
• Throw an error if an invalid UTF-8 character is encountered
• Tag version 1.0.0

This project publishes no release notes. Between 0.0.5 and 0.0.6 there were 5 commits, 3 of them substantive:

• Fix typo in null states
• Track the stream offset during parsing.
• Fix offset tracking for escaped sequences.

This project publishes no release notes. Between 0.0.4 and 0.0.5 there were 4 commits, 2 of them substantive:

• added new utf8 test cases that simulate 1-4 byte utf8 characters being chunked before their boundaries are reached, which leads the subsequent call to buffer.toString() to display two-four replacement characters: �� instead of the proper representation of the multi-byte characters that were actually passed to the parser
• added detection & correction of multi-byte utf8 characters that are split up (when chunked in stream buffers) before the character boundary is met, this commit passes existing tests and new tests written for this use case

This project publishes no release notes. Between 0.0.3 and 0.0.4 there were 13 commits, 11 of them substantive:

• make room for more tests
• commented code will live forever in the git history
• require() the json file for later when this test will run in browsers
• remove more superfluous test code
• more machine-readable test output
• passing tap test
• remove superfluous json load in the primitives test
• devDependencies and scripts.test
• failing utf8 test
• add utf8 support
• more passing utf8 tests

This project publishes no release notes. Between 0.0.2 and 0.0.3 there were 4 commits, 2 of them substantive:

• Replace all swith/case statements by the equivalent with if/else if/else in the method proto.onToken.
• Replace all switch/case statements by the equivalent with if/else if/else in the method proto.write.

This project publishes no release notes. Between v0.0.1 and 0.0.2 there were 11 commits, 7 of them substantive:

• Move logs to end
• Add proper UTF8 support instead of accidental
• Add twitterfeed example
• Remove utf8 decoding and allow strings as input
• Fixed typo that broke parsing of number literals in exponential notation with + or - after e or E.
• Update master
• add LICENSE and license directive to package.json, per README