fix(deps): update dependency @tinymce/tinymce-react to v3.14.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@tinymce/tinymce-react	3.8.4 -> 3.14.0

---

Release Notes

tinymce/tinymce-react (@​tinymce/tinymce-react)

v3.14.0

Compare Source

Changed

• Allow react version "^18.0.0"

Fixed

• Updated dependencies.

v3.13.1

Compare Source

Fixed

• Updated dependencies
• Use editor.mode.set(...) when available instead of the deprecated editor.setMode(..) which will be removed in TinyMCE 6.
• Addressed lint errors

v3.13.0

Compare Source

Added

• Added new rollback prop for changing the delay after which a rollback is performed (when value and editor content don't match) or disabling it completely.

v3.12.8

Compare Source

Changed

• Wait 10 seconds (increased from 1) for the target element to be in the DOM before giving up.

Fixed

• Updated dependencies.

v3.12.7

Compare Source

Fixed

• The integration will now initialize in a shadow dom.
• Updated dependencies

v3.12.6

Compare Source

Fixed

• As the tinymce dependency is only used for types allow all versions after 5.5.1 when types were first added, but prefer the latest when unspecified.

v3.12.5

Compare Source

Fixed

• Fixed ignoring the toolbar prop when it contains a falsy value when it should only be ignored if it is undefined or null.
• Ensure that the editor is initialized attached to a document.
• Updated dependencies

v3.12.4

Compare Source

Fixed

• Allow use of react version "^16.7.0" as well as "^17.0.1" to correct the unintended breaking change introduced in release 3.9.
• Updated dependencies

v3.12.3

Compare Source

Fixed

• Avoid trying to get a bookmark for an unfocused inline editor
• Recreated the storybook examples in the new recommend format as the format we were using broke on an upgrade
• Updated dependencies

v3.12.2

Compare Source

Fixed

• Slowed down the change rollback to 200 milliseconds to allow async frameworks a chance to set the value. #INT-2475
• Fixed cursor position recording for rolling back formatting-only changes.
• Updated dependencies

v3.12.1

Compare Source

Fixed

• Re-added change event as a trigger of onEditorChange so toggling formatting will be detected. #INT-2473
• Defer evaluating browser capabilities until after the component has mounted to allow server side rendering. #INT-2472

v3.12.0

Compare Source

Added

• Storybook demo for a controlled component with a fixed value. INT-2352
• Storybook demo for a controlled component with a maximum length. INT-2462

Changed

• When used as a controlled component the editor will rollback a change if it is not set via the value prop within a millisecond. INT-2352

v3.11.1

Compare Source

Fixed

• Stopped inline editor grabbing focus when the value is set
• Caught exceptions thrown while trying to restore selection after setting content

v3.11.0

Compare Source

Changed

• Updates to initialValue after editor initialization will now be detected and applied and will result in a complete reset of undo state. #INT-2367
• During componentDidUpdate the value prop will be applied if it is different to the current editor content even when it is not different to the previous value of the value prop. #INT-2372

Fixed

• Apply changes to initialValue, value and disabled which occur between editor setup and initialization that were previously ignored. #INT-2371
• An attempt will be made to retain the cursor position when the value prop forces an update to the editor content. If the cursor position can not be found it will return to the start of the document as before. #INT-2370
• Internal tracking of the current content is now always done in HTML so outputFormat should not cause any unexpected behavior. #INT-2369

Deprecated

• The outputFormat prop will be removed in a future release. If text output is required call editor.getContent({ format: 'text' }) in any of the event callbacks. #INT-2368

v3.10.4

Compare Source

Fixed

• Check for editor changes on "compositionend" event to more accurately trigger onEditorChange. #INT-2348
• Updated dependencies to latest available

v3.10.3

Compare Source

Fixed

• Updated dependencies to latest available

v3.10.2

Compare Source

Fixed

• Event handlers are registered at setup time so props like onBeforeRenderUI will now be called. #INT-2325

v3.10.1

Compare Source

Fixed

• Fixed CI build

v3.10.0

Compare Source

Fixed

• Fixed event binding to lookup handlers at call time instead of rebinding on every change.

v3.9.0

Compare Source

Changed

• Adopted beehive-flow branching and versioning process/tooling.
• Changed the changelog formatting
• Updated dependencies to latest available

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @edx/[email protected]
npm ERR! Found: @edx/[email protected]
npm ERR! node_modules/@edx/frontend-build
npm ERR!   dev @edx/frontend-build@"12.9.0-alpha.6" from the root project
npm ERR!   peer @edx/frontend-build@">= 8.1.0 || ^12.9.0-alpha.1" from @edx/[email protected]
npm ERR!   node_modules/@edx/frontend-platform
npm ERR!     @edx/frontend-platform@"4.6.1" from the root project
npm ERR!     peer @edx/frontend-platform@"^4.0.0 || ^5.0.0" from @edx/[email protected]
npm ERR!     node_modules/@edx/frontend-component-footer
npm ERR!       @edx/frontend-component-footer@"12.2.1" from the root project
npm ERR!     1 more (@edx/frontend-component-header)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @edx/frontend-build@">=8.1.0" from @edx/[email protected]
npm ERR! node_modules/@edx/react-unit-test-utils
npm ERR!   @edx/react-unit-test-utils@"1.7.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @edx/[email protected]
npm ERR! node_modules/@edx/frontend-build
npm ERR!   peer @edx/frontend-build@">=8.1.0" from @edx/[email protected]
npm ERR!   node_modules/@edx/react-unit-test-utils
npm ERR!     @edx/react-unit-test-utils@"1.7.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/6d357b/9970b5/cache/others/npm/_logs/2023-09-04T04_43_59_172Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/6d357b/9970b5/cache/others/npm/_logs/2023-09-04T04_43_59_172Z-debug-0.log