fix: Don't init when editor is destroyed

[tomi-bigpi]

Please describe your changes

Adds a check to see if the EditorContent editor is already destroyed when init is called. This can happen due to using React.StrictMode where the editor is re-rendered back-to-back automatically by React.

How did you accomplish your changes

Extended the existing check to include verifying that the editor hasn't already been destroyed.

How have you tested your changes

Manual testing.

How can we verify your changes

Unfortunately, I don't have a clean reproduction available at this time.

Remarks

Checklist

• The changes are not breaking the editor
• Added tests where possible
• Followed the guidelines
• Fixed linting issues

Related issues

This issue is similar to the various problems described in #1451 (and other linked issues in that thread) and manifests itself with the same TypeError: Cannot read property 'matchesNode' of null.

[netlify]

✅ Deploy Preview for tiptap-embed ready!

Name	Link
🔨 Latest commit	1bce804
🔍 Latest deploy log	https://app.netlify.com/sites/tiptap-embed/deploys/64596a4b62a6ba0008c132d1
😎 Deploy Preview	https://deploy-preview-4029--tiptap-embed.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[gl3nn]

We are currently seeing an error that might be fixed by this. It only occurs with strict mode on; and it is clear that the editor is destroyed in the stack trace. Did you find a temporary work around?

[tomi-bigpi]

We are currently seeing an error that might be fixed by this. It only occurs with strict mode on; and it is clear that the editor is destroyed in the stack trace. Did you find a temporary work around?

We're still patching this locally...