Prevent immer from freeze operations.

[ulion]

Is this adding or improving a feature or fixing a bug?

Fixing a bug.

What's the new behavior?

After copy (editor.getFragment), the editor.operations is not frozen (then no crash due to any update). if in case you actually using immer 7+ though Slate using v5 but if the client code has other dependencies which using higher version of immer, finally the Slate could actually calling immer 7+.

How does this change work?

Like https://github.com/ianstormtaylor/slate/pull/3850/files#r480954559 suggested, but without upgrade the immer version in package.json

Have you checked that...?

• The new code matches the existing patterns and styles.
• The tests pass with yarn test.
• The linter passes with yarn lint. (Fix errors with yarn fix.)
• The relevant examples still work. (Run examples with yarn start.)

Does this fix any issues or need any specific reviewers?

Fixes: #4034
Reviewers: @BrentFarese

[BrentFarese]

Is Immer freezing editor.operations caused by the bump in Immer in 60.1 from 5.0.0 to 5.3.6? Do you know @ulion? Also, I'm probably inclined to merge #3850 as this is a duplicate?

[ulion]

Is Immer freezing editor.operations caused by the bump in Immer in 60.1 from 5.0.0 to 5.3.6? Do you know @ulion? Also, I'm probably inclined to merge #3850 as this is a duplicate?

should be immer 7.0 issue. since other packages in my project use immer 7.0, I think sometimes no matter which version slate using, it is effected.

[ulion]

well, I am not sure, since I only have a mixed immer 7 env. if you have pure 0.60.1 test env, simply copy then click anywhere will tell us whether it's effected.

[BrentFarese]

well, I am not sure, since I only have a mixed immer 7 env. if you have pure 0.60.1 test env, simply copy then click anywhere will tell us whether it's effected.

K. Going to close this as it's a duplicate of #3850 and will merge #3850 once the PR owner answers a question(s) I had. Will get this fix + the Immer version bump in though soon! Thanks.