Show errors when settings exports fail

[Shreya-nipunge]

Description

This is related to #311, but focuses specifically on user-triggered export actions in main.js and missing inline Settings UI feedback, not internal settingsStore save methods.

The theme profile export and full settings backup export handlers write files with writeFileSync() without catching errors. If the selected destination is unwritable or the write fails, the IPC call can reject and the Settings UI may show no clear failure message.

Affected Areas

• theme-profiles:export IPC handler
• settings:export-all IPC handler
• Export actions in settings.js

Steps to Reproduce

1. Open Paraline Settings and create or select a theme profile.
2. Click Export Theme Profile or Export All Settings.
3. Choose a destination where the application cannot write, such as a protected folder, read-only location, or locked file path.

Expected Behaviour

The export handler should catch write errors and return a structured failure response (for example, { success: false, error: "..." }). The Settings UI should display a clear error message explaining that the export failed and why.

Actual Behaviour

The export handlers write files directly with writeFileSync(). If the write operation fails, the IPC invocation can reject, resulting in inconsistent or missing user-facing error feedback.

Environment

• OS: Windows
• Node Version: v22.17.0
• Electron Version: ^37.0.0
• Repo Version / Commit: v2.2.0 / dbaae83

[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 👍

[Shreya-nipunge]

Hi @SamXop123 ,

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

Could you please assign this issue to me?

Thank you!