Use @streamparser/json if the input is too large to fit in a V8 string

[mstange]

Here's a file which decompresses to a 605.8MB JSON string: large-speedometer3-profile.json.gz

Loading this file in Chrome, or in node via profiler-edit, fails due to the string size.

As a workaround we can use a streaming JSON parser which doesn't materialize a string for the entire thing.

[codecov]

Codecov Report

❌ Patch coverage is 63.63636% with 12 lines in your changes missing coverage. Please review.
✅ Project coverage is 83.77%. Comparing base (45ad149) to head (41473d3).
⚠️ Report is 3 commits behind head on main.

Files with missing lines	Patch %	Lines
src/profile-logic/process-profile.ts	63.63%	12 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6016      +/-   ##
==========================================
- Coverage   83.79%   83.77%   -0.02%     
==========================================
  Files         329      329              
  Lines       34395    34423      +28     
  Branches     9514     9627     +113     
==========================================
+ Hits        28821    28839      +18     
- Misses       5145     5155      +10     
  Partials      429      429              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[fatadel]

Looks good to me personally, but Claude found a minor issue:

V8_STRING_MAX_SIZE is slightly above the actual V8 limit. The constant is 512 * 1024 * 1024 - 1 = (1 << 29) - 1 = 536870911. V8's String::kMaxLength under pointer compression (the typical config — buffer.constants.MAX_STRING_LENGTH exposes this in Node) is (1 << 29) - 24 = 536870888. That leaves a ~23-byte window where the size check passes but the ASCII-decoded string would still throw RangeError: Invalid string length. Practically irrelevant, but the fix is trivial: (1 << 29) - 24, or just import buffer.constants.MAX_STRING_LENGTH in Node paths.

[mstange]

Hah, oops.