Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 3, 2023

This PR contains the following updates:

Package Change Age Confidence
react-markdown ^8.0.0 -> ^10.0.0 age confidence

Release Notes

remarkjs/react-markdown (react-markdown)

v10.1.0

Compare Source

Add
Fix

Full Changelog: remarkjs/react-markdown@10.0.1...10.1.0

v10.0.1

Compare Source

Full Changelog: remarkjs/react-markdown@10.0.0...10.0.1

v10.0.0

Compare Source

  • aaaa40b
    Remove support for className prop
    migrate: see “Remove className” below
Remove className

The className prop was removed.
If you want to add classes to some element that wraps the markdown
you can explicitly write that element and add the class to it.
You can then choose yourself which tag name to use and whether to add other
props.

Before:

<Markdown className="markdown-body">{markdown}</Markdown>

After:

<div className="markdown-body">
  <Markdown>{markdown}</Markdown>
</div>

v9.1.0

Compare Source

  • 6ce120e
    Add support for async plugins

v9.0.3

Compare Source

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

v9.0.2

Compare Source

  • b151a90
    Fix types for React 19
  • 6962af7
    Add declaration maps
  • aa5933b
    Refactor to use @import to import types

v9.0.1

Compare Source

  • d8e3787
    Fix double encoding in new url transform

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() {
  /**
   * @&#8203;param {import('hast').Root} tree
   * @&#8203;returns {undefined}
   */
  return function (tree) {
    visit(tree, function (node, index) {
      if (node.type === 'element' && typeof index === 'number') {
        node.properties.index = 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() {
  /**
   * @&#8203;param {import('hast').Root} tree
   * @&#8203;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 - "before 7am" in timezone Europe/Madrid, 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.

@renovate renovate bot enabled auto-merge (rebase) December 3, 2023 23:06
@renovate
Copy link
Contributor Author

renovate bot commented Dec 3, 2023

⚠ 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 unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^17.0.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@">=18" from [email protected]
npm ERR! node_modules/react-markdown
npm ERR!   react-markdown@"^9.0.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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-05-09T07_59_19_382Z-debug-0.log

@renovate
Copy link
Contributor Author

renovate bot commented May 9, 2024

⚠️ 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 unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^17.0.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@">=18" from [email protected]
npm ERR! node_modules/react-markdown
npm ERR!   react-markdown@"^10.0.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! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-11-16T13_08_31_471Z-debug-0.log

@renovate renovate bot changed the title fix(deps): update dependency react-markdown to v9 fix(deps): update dependency react-markdown to v10 Feb 20, 2025
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants