SEA: preserve raw strings with decrypt skipParse option - #1427
Open
tmsteph wants to merge 1 commit into
Open
Conversation
tmsteph
marked this pull request as ready for review
August 22, 2026 14:26
This file contains hidden or 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
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.
What changed
Adds an opt-in
skipParseoption toSEA.decryptso callers can recover plaintext strings exactly as encrypted, even when the string happens to look like JSON.The default behavior is unchanged for backwards compatibility: decrypted plaintext still passes through
SEA.opt.parseunlessskipParseis explicitly enabled.Example:
This updates both the canonical
sea.jsbundle and extractedsea/decrypt.js, exposes the callback/options arguments in the TypeScript declarations, and adds regression coverage for JSON-looking string payloads.Fixes #1418.
Validation
npm run testsea: 36 passing, 1 pending, including the newskipParseregression.test/sea/nodeauth.js: all 5 visible scenarios passed on the first clean run. The harness intentionally callsprocess.exit(-1)in itsafterhook, so it exits with status 255 after the tests.git diff --check: clean.