You'll notice
Useful3 Signal1
Plugin and marketplace manifests with hidden leading characters now parse instead of failing.
What's wrong with this entry?
Anonymous. No account, no email.
What
Plugin manifests, marketplace manifests and the plugin scan for MCP servers now pass the file text through a normalising helper before parsing it, instead of parsing the raw bytes. Manifests that previously failed to load, most likely ones carrying a byte-order mark or other hidden leading characters, can now parse. The failure message is unchanged.
Details
- Failures still report as
Invalid JSON syntax:followed by the parser error. - The exact normalisation the helper performs is not pinned down in the bundle; stripping a leading byte-order mark is the likely intent.
Evidence
r = lt(cy(e));, Invalid JSON syntax: , plugin-json
Strings lifted out of the shipped bundle, so the claim above can be checked against them.