chore(deps-dev): bump markdown-to-jsx from 7.1.2 to 7.7.3

[dependabot]

Bumps markdown-to-jsx from 7.1.2 to 7.7.3.

Release notes

Sourced from markdown-to-jsx's releases.

v7.7.3

Patch Changes

• 8026103: Handle paragraph splitting better, fixes #641.
• 1ea00bb: Adjust table row parsing to better handle inline syntaxes and improve performance.

v7.7.2

Patch Changes

• 52a727c: Use ReactNode instead of ReactChild for React 19 compatibility
• 4fa87d8: Bump ws from 8.11.0 to 8.18.0

v7.7.1

Patch Changes

• 9d42449: Factor out unnecessary element cloning.
• 8920038: Remove use of explicit React.createElement.

v7.7.0

Minor Changes

• 20777bf: Add support for GFM alert-style blockquotes.

  > [!Note]
  > This is a note-flavored alert blockquote. The "Note" text is injected as a `<header>` by
  > default and the blockquote can be styled via the injected class `markdown-alert-note`
  > for example.

Patch Changes

• 5d7900b: Adjust type signature for <Markdown> component to allow for easier composition.
• 918b44b: Use newer React.JSX.* namespace instead of JSX.* for React 19 compatibility.
• 91a5948: Arbitrary HTML no longer punches out pipes when parsing rows. If you absolutely need a pipe character that isn't a table separator, either escape it or enclose it in backticks to trigger inline code handling.
• 23caecb: Drop encountered ref attributes when processing inline HTML, React doesn't handle it well.

v7.6.2

Patch Changes

• 0274445: Fix false detection of tables in some scenarios.
• 69f815e: Handle class attribute from arbitrary HTML properly to avoid React warnings.
• 857809a: Fenced code blocks are now tolerant to a missing closing sequence; this improves use in LLM scenarios where the code block markdown is being streamed into the editor in chunks.

v7.6.1

Patch Changes

• 87d8bd3: Handle class attribute from arbitrary HTML properly to avoid React warnings.

v7.6.0

... (truncated)

Changelog

Sourced from markdown-to-jsx's changelog.

7.7.3

Patch Changes

• 8026103: Handle paragraph splitting better, fixes #641.
• 1ea00bb: Adjust table row parsing to better handle inline syntaxes and improve performance.

7.7.2

Patch Changes

• 52a727c: Use ReactNode instead of ReactChild for React 19 compatibility
• 4fa87d8: Bump ws from 8.11.0 to 8.18.0

7.7.1

Patch Changes

• 9d42449: Factor out unnecessary element cloning.
• 8920038: Remove use of explicit React.createElement.

7.7.0

Minor Changes

• 20777bf: Add support for GFM alert-style blockquotes.

  > [!Note]
  > This is a note-flavored alert blockquote. The "Note" text is injected as a `<header>` by
  > default and the blockquote can be styled via the injected class `markdown-alert-note`
  > for example.

Patch Changes

• 5d7900b: Adjust type signature for <Markdown> component to allow for easier composition.
• 918b44b: Use newer React.JSX.* namespace instead of JSX.* for React 19 compatibility.
• 91a5948: Arbitrary HTML no longer punches out pipes when parsing rows. If you absolutely need a pipe character that isn't a table separator, either escape it or enclose it in backticks to trigger inline code handling.
• 23caecb: Drop encountered ref attributes when processing inline HTML, React doesn't handle it well.

7.6.2

Patch Changes

• 0274445: Fix false detection of tables in some scenarios.
• 69f815e: Handle class attribute from arbitrary HTML properly to avoid React warnings.
• 857809a: Fenced code blocks are now tolerant to a missing closing sequence; this improves use in LLM scenarios where the code block markdown is being streamed into the editor in chunks.

7.6.1

... (truncated)

Commits

• 3cfd019 Version Packages (#647)
• 8026103 fix: #641 (#648)
• 02c883b chore: put const back
• 50ccf2e refactor: further simplify
• 1ea00bb chore: changeset
• a271bb4 refactor: collapse loop handling for perf
• 420251e fix: #644 parsing issue inside table rows
• b732c6f chore: add llm instructions
• 0441c71 chore: upgrade yarn
• c2ec5aa Version Packages (#637)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[netlify]

✅ Check the deploy log for errors here: https://app.netlify.com/sites/fundamental-styles/deploys

Name	Link
🔨 Latest commit	bc88a25
🔍 Latest deploy log	https://app.netlify.com/sites/fundamental-styles/deploys/67839f312d23a00008af43c8

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.