Update dependency codemirror to v5.65.18

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
codemirror	5.65.14 -> 5.65.18

---

Release Notes

codemirror/basic-setup (codemirror)

v5.65.18

Compare Source

v5.65.17

Compare Source

v5.65.16

Compare Source

v5.65.15

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
azure-auth-api-test	❌ Failed (Inspect)			Sep 23, 2024 1:08pm

[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: @vtfk/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"18.1.0" from the root project
npm ERR!   peer react@"^16.14.0 || ^17.0.0 || ^17.0.1 || ^17.0.1 || ^17.0.1 || ^18.0.0" from @vtfk/[email protected]
npm ERR!   node_modules/@vtfk/components
npm ERR!     @vtfk/components@"0.8.1" from the root project
npm ERR!   7 more (react-dom, react-popper, react-router, react-router-dom, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.0.0 || ^17.0.0" from @vtfk/[email protected]
npm ERR! node_modules/@vtfk/react-msal
npm ERR!   @vtfk/react-msal@"2.0.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^16.0.0 || ^17.0.0" from @vtfk/[email protected]
npm ERR!   node_modules/@vtfk/react-msal
npm ERR!     @vtfk/react-msal@"2.0.3" 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/e7b21f/f7fd36/cache/others/npm/_logs/2023-11-23T10_00_44_660Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/e7b21f/f7fd36/cache/others/npm/_logs/2023-11-23T10_00_44_660Z-debug-0.log

[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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @vtfk/[email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error   react@"18.1.0" from the root project
npm error   peer react@"^16.14.0 || ^17.0.0 || ^17.0.1 || ^17.0.1 || ^17.0.1 || ^18.0.0" from @vtfk/[email protected]
npm error   node_modules/@vtfk/components
npm error     @vtfk/components@"0.8.1" from the root project
npm error   7 more (react-dom, react-popper, react-router, react-router-dom, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.0.0 || ^17.0.0" from @vtfk/[email protected]
npm error node_modules/@vtfk/react-msal
npm error   @vtfk/react-msal@"2.0.3" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"^16.0.0 || ^17.0.0" from @vtfk/[email protected]
npm error   node_modules/@vtfk/react-msal
npm error     @vtfk/react-msal@"2.0.3" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-09-23T13_08_38_462Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-09-23T13_08_38_462Z-debug-0.log