Skip to content

fix: keep fast parser behavior in parity with classic parser - #1046

Closed
amtbsl wants to merge 2 commits into
motdotla:masterfrom
amtbsl:fix/fast-parser-parity-1043
Closed

amtbsl wants to merge 2 commits into
motdotla:masterfrom
amtbsl:fix/fast-parser-parity-1043

Conversation

@amtbsl

@amtbsl amtbsl commented Aug 29, 2026

Copy link
Copy Markdown

Summary

  • fall back to the classic parser for JavaScript whitespace cases the fast path cannot safely handle
  • preserve quoted values that begin after a newline
  • treat junk after a closing quote like the classic parser
  • add focused parser parity regressions

Testing

  • npm test (203 passed, 1 skipped)
  • npm run lint
  • type check and targeted fuzz regression

Fixes #1043

@motdotla

Copy link
Copy Markdown
Owner

fixing here and will go out with next patch: #1056

@motdotla motdotla closed this Sep 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fast parser diverges from the default parser (silent value loss)

2 participants