-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
fix: handle UTF-8 BOM in JSON parsing #10269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
murataslan1
wants to merge
2
commits into
parcel-bundler:v2
Choose a base branch
from
murataslan1:fix/utf8-bom-handling
base: v2
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| // @flow strict-local | ||
|
|
||
| // UTF-8 BOM (Byte Order Mark) is the character \uFEFF at the start of a file. | ||
| // Some editors on Windows (like Visual Studio) add this to UTF-8 files. | ||
| // This function strips it if present to prevent JSON parse errors. | ||
|
|
||
| export default function stripBOM(content: string): string { | ||
| // 0xFEFF is the UTF-8 BOM character code | ||
| if (content.charCodeAt(0) === 0xfeff) { | ||
| return content.slice(1); | ||
| } | ||
| return content; | ||
| } | ||
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,36 @@ | ||
| // @flow strict-local | ||
|
|
||
| import assert from 'assert'; | ||
| import stripBOM from '../src/stripBOM'; | ||
|
|
||
| describe('stripBOM', () => { | ||
| it('should strip UTF-8 BOM from the start of a string', () => { | ||
| const withBOM = '\uFEFF{"name": "test"}'; | ||
| const result = stripBOM(withBOM); | ||
| assert.strictEqual(result, '{"name": "test"}'); | ||
| }); | ||
|
|
||
| it('should not modify strings without BOM', () => { | ||
| const withoutBOM = '{"name": "test"}'; | ||
| const result = stripBOM(withoutBOM); | ||
| assert.strictEqual(result, '{"name": "test"}'); | ||
| }); | ||
|
|
||
| it('should handle empty strings', () => { | ||
| const empty = ''; | ||
| const result = stripBOM(empty); | ||
| assert.strictEqual(result, ''); | ||
| }); | ||
|
|
||
| it('should only strip BOM at the beginning', () => { | ||
| const bomInMiddle = '{"name": "\uFEFFtest"}'; | ||
| const result = stripBOM(bomInMiddle); | ||
| assert.strictEqual(result, '{"name": "\uFEFFtest"}'); | ||
| }); | ||
|
|
||
| it('should allow JSON.parse to work after stripping BOM', () => { | ||
| const withBOM = '\uFEFF{"name": "test", "version": "1.0.0"}'; | ||
| const result = JSON.parse(stripBOM(withBOM)); | ||
| assert.deepStrictEqual(result, {name: 'test', version: '1.0.0'}); | ||
| }); | ||
| }); |
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 was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The BOM constant is defined but never used in the code. The implementation directly uses 0xfeff in the comparison on line 9. Consider either using the constant in the comparison (content.charCodeAt(0) === BOM.charCodeAt(0)) or removing the constant definition if it's not needed.