BUG-001: JSON.stringify-keyed option diff can cause data loss / stale config

[ApexYash11]

Summary

The wrapper diffs prop changes by stringifying option objects and comparing the strings (src/ImageEditor.tsx, remountKey / updatableKey). This is fragile and can cause bad behavior.

Severity: P1 (correctness / data loss)

Problem

• Key-order sensitivity — semantically identical options objects that differ only in property declaration order produce different strings → a spurious remount (the README explicitly warns remount-tier options destroy unsaved edits, so this is silent data loss) or a spurious updateOptions call.
• Drops undefined / functions — JSON.stringify silently omits them, so real changes inside options can be invisible to the diff → stale editor configuration without any warning.
• Throws on circular references — a circular reference inside options crashes during render.

Verification

• Code-proven from src/ImageEditor.tsx (lines around remountKey / updatableKey). Reproduced logically; no runtime repro shipped.

Suggested fix

Use structural deep-equality or a canonical form (stable, sorted-key serialization); compare values, not raw strings. Keep the repo's 100% coverage threshold by adding tests for the key-order and dropped-field cases.

[ApexYash11]

Hi maintainers 👋

I'd like to pick this up and work on BUG-001. Could I be assigned to it?

Proposed approach

1. Replace the fragile JSON.stringify-based prop diff (remountKey / updatableKey in src/ImageEditor.tsx) with a structural deep-equality comparison, so semantically identical options don't trigger a spurious remount (which loses unsaved edits) and dropped undefined/function fields don't leave the editor stale.
2. Handle the circular-reference crash defensively.
3. Keep the repo's 100% coverage threshold — I'll add targeted tests for the key-order and dropped-field cases.

Happy to open a PR that references this issue once assigned. Thanks!