Validate JSON structure of exported settings backup files

[Kirtan-pc]

Description

If a user imports a settings backup file that has syntactically invalid JSON structure, the JSON.parse call in main.js throws an unhandled exception. This returns a raw syntax error exception string to the settings page instead of a user-friendly error banner.

Steps to Reproduce

1. Create a backup JSON file and introduce a syntax error (e.g., leave a trailing comma or omit a closing brace).
2. Click "Import Settings Backup" and select the malformed file.
3. Observe the error toast displaying raw Node.js parsing exception messages (e.g., Unexpected token } in JSON...).

Expected Behaviour

The import handler should catch JSON parsing errors specifically and return a friendly error message indicating that the backup file is corrupt or malformed.

Actual Behaviour

Raw JavaScript/Node.js stack traces and parser exceptions are bubbled directly to the UI.

[github-actions]

Thanks for opening this issue and contributing to Paraline 🌌

The maintainers will review it soon.
If applicable, please make sure to include:

• clear reproduction/details
• screenshots or recordings
• implementation ideas (optional but appreciated)

Thanks again for helping improve the project 👍

[Kirtan-pc]

Hi @SamXop123 ,

I would like to work on this issue under GSSoC 2026.

Could you please assign this issue to me?

Thank you!