Skip to content

fix: strip leading UTF-8 BOM#32

Merged
Marsup merged 1 commit into
masterfrom
fix/bom
Jul 1, 2026
Merged

fix: strip leading UTF-8 BOM#32
Marsup merged 1 commit into
masterfrom
fix/bom

Conversation

@Marsup

@Marsup Marsup commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Fixes #28

@Marsup Marsup self-assigned this Jul 1, 2026
@Marsup Marsup added the feature New functionality or improvement label Jul 1, 2026
@Marsup Marsup added this to the 4.0.0 milestone Jul 1, 2026
@Marsup Marsup merged commit a10bbf6 into master Jul 1, 2026
12 checks passed
@Marsup Marsup deleted the fix/bom branch July 1, 2026 12:31

@kanongil kanongil left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don’t like this feature.

It extends the functionality of the module in a non-obvious way just to handle input that has clearly been authored wrong.

Also with this change, it is no longer a drop-in replacement for JSON.parse(), so the docs needs to be updated to reflect this.

@Marsup

Marsup commented Jul 2, 2026

Copy link
Copy Markdown
Contributor Author

My bad, I thought the MAY in the spec wasn't prohibiting it, but it seems the consensus is not to do it. I'll revert.

@Marsup Marsup removed this from the 4.0.0 milestone Jul 2, 2026
@Marsup Marsup added this to the 4.0.0 milestone Jul 2, 2026
@Marsup Marsup mentioned this pull request Jul 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature New functionality or improvement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Ignore BOM char

2 participants