Fix for no-uncaught-json-parse warnings

Editor assessment

`refactor` is a defensible choice here because addressing `no-uncaught-json-parse` warnings presumably reshapes parsing code without changing behavior, though some teams would file lint-driven adjustments under `style` or `chore`. The `core` scope is appropriate. The subject's phrasing, 'fix for no-uncaught-json-parse warnings', is awkward and vague: 'fix for' muddies the imperative mood and the lint rule name alone tells readers little about which code paths gained explicit JSON error handling. Lowercase start and the absence of a trailing period are correct, and at roughly 55 characters truncation is not a concern. A body naming the affected modules and why the warnings mattered would add real value.