Update dependency react-markdown to v9

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-markdown	8.0.7 -> 9.0.3

---

Release Notes

remarkjs/react-markdown (react-markdown)

v9.0.3

Compare Source

(same as 9.0.2 but now with d.ts files)

Full Changelog: remarkjs/react-markdown@9.0.2...9.0.3

v9.0.2

Compare Source

Types

• b151a90 Fix types for React 19
  by @​remcohaszing in https://github.com/remarkjs/react-markdown/pull/879
• 6962af7 Add declaration maps
• aa5933b Refactor to use @import to import types
  by @​remcohaszing in https://github.com/remarkjs/react-markdown/pull/836

Miscellaneous

• 9eb589e Fix typo in changelog
  by @​NicholasWilsonDEV in https://github.com/remarkjs/react-markdown/pull/874
• 515bf19 Fix typo
  by @​deep-lyra in https://github.com/remarkjs/react-markdown/pull/868

Full Changelog: remarkjs/react-markdown@9.0.1...9.0.2

v9.0.1

Compare Source

• d8e3787 Fix double encoding in new url transform
• 55d8d83 Refactor docs to use createRoot

Full Changelog: remarkjs/react-markdown@9.0.0...9.0.1

v9.0.0

Compare Source

• b67d714
  Change to require Node.js 16
  migrate: update too
• ec2b134
  Change to require React 18
  migrate: update too
• bf5824f
  Change to use exports
  migrate: don’t use private APIs
• c383a45
  Update @types/hast, utilities, plugins, etc
  migrate: update too
• eca5e6b
08ead9e
  Replace transformImageUri, transformLinkUri w/ urlTransform
  migrate: see “Add urlTransform” below
• de29396
  Remove linkTarget option
  migrate: see “Remove linkTarget” below
• 4346276
  Remove support for passing custom props to components
  migrate: see “Remove includeElementIndex”, “Remove rawSourcePos”,
  “Remove sourcePos”, “Remove extra props passed to certain components”
  below
• c0dfbd6
  Remove UMD bundle from package
  migrate: use esm.sh or a CDN or so
• e12b5e9
  Remove prop-types
  migrate: use TypeScript
• 4eb7aa0
  Change to throw errors for removed props
  migrate: don’t pass options that don’t do things
• 8aabf74
  Change to improve error messages
  migrate: expect better messages

Add urlTransform

The transformImageUri and transformLinkUri were removed.
Having two functions is a bit much, particularly because there are more URLs
you might want to change (or which might be unsafe so we make them safe).
And their name and APIs were a bit weird.
You can use the new urlTransform prop instead to change all your URLs.

Remove linkTarget

The linkTarget option was removed; you should likely not set targets.
If you want to, use
rehype-external-links.

Remove includeElementIndex

The includeElementIndex option was removed, so index is never passed to
components.
Write a plugin to pass index:

Show example of plugin

import {visit} from 'unist-util-visit'

function rehypePluginAddingIndex() {
  /**
   * @​param {import('hast').Root} tree
   * @​returns {undefined}
   */
  return function (tree) {
    visit(tree, function (node, index) {
      if (node.type === 'element' && typeof index === 'number') {
        node.properties === index
      }
    })
  }
}

Remove rawSourcePos

The rawSourcePos option was removed, so sourcePos is never passed to
components.
All components are passed node, so you can get node.position from them.

Remove sourcePos

The sourcePos option was removed, so data-sourcepos is never passed to
elements.
Write a plugin to pass index:

Show example of plugin

import {stringifyPosition} from 'unist-util-stringify-position'
import {visit} from 'unist-util-visit'

function rehypePluginAddingIndex() {
  /**
   * @​param {import('hast').Root} tree
   * @​returns {undefined}
   */
  return function (tree) {
    visit(tree, function (node) {
      if (node.type === 'element') {
        node.properties.dataSourcepos = stringifyPosition(node.position)
      }
    })
  }
}

Remove extra props passed to certain components

When overwriting components, these props are no longer passed:

• inline on code
  — create a plugin or use pre for the block
• level on h1, h2, h3, h4, h5, h6
  — check node.tagName instead
• checked on li
  — check task-list-item class or check props.children
• index on li
  — create a plugin
• ordered on li
  — create a plugin or check the parent
• depth on ol, ul
  — create a plugin
• ordered on ol, ul
  — check node.tagName instead
• isHeader on td, th
  — check node.tagName instead
• isHeader on tr
  — create a plugin or check children

---

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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)
charlottestuby	❌ Failed (Inspect)			Jan 6, 2025 1:31pm

[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 warn cli npm v11.0.0 does not support Node.js v20.7.0. This version of npm supports the following node versions: `^20.17.0 || >=22.9.0`. You can find the latest version at https://nodejs.org/.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: decap-cms-app@3.0.12
npm error Found: react@18.2.0
npm error node_modules/react
npm error   react@"18.2.0" from the root project
npm error   peer react@">=16.8.0" from @dnd-kit/accessibility@3.0.1
npm error   node_modules/@dnd-kit/accessibility
npm error     @dnd-kit/accessibility@"^3.0.0" from @dnd-kit/core@6.0.8
npm error     node_modules/@dnd-kit/core
npm error       peer @dnd-kit/core@"^6.0.6" from @dnd-kit/modifiers@6.0.1
npm error       node_modules/@dnd-kit/modifiers
npm error         @dnd-kit/modifiers@"^6.0.1" from decap-cms-widget-file@3.0.4
npm error         node_modules/decap-cms-app/node_modules/decap-cms-widget-file
npm error         2 more (decap-cms-widget-list, decap-cms-widget-relation)
npm error       4 more (@dnd-kit/sortable, decap-cms-widget-file, ...)
npm error   36 more (@dnd-kit/core, @dnd-kit/modifiers, @dnd-kit/sortable, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.8.4 || ^17.0.0" from decap-cms-app@3.0.12
npm error node_modules/decap-cms-app
npm error   decap-cms-app@"3.0.12" from the root project
npm error
npm error Conflicting peer dependency: react@17.0.2
npm error node_modules/react
npm error   peer react@"^16.8.4 || ^17.0.0" from decap-cms-app@3.0.12
npm error   node_modules/decap-cms-app
npm error     decap-cms-app@"3.0.12" 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/2025-01-06T13_30_42_971Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-06T13_30_42_971Z-debug-0.log