[Snyk] Upgrade markdown-to-jsx from 7.3.2 to 7.4.7

[syofyanzuhad]

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade markdown-to-jsx from 7.3.2 to 7.4.7.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 8 versions ahead of your current version.

• The recommended version was released on 3 months ago.

Release notes

Package name: markdown-to-jsx

• 7.4.7 - 2024-04-13
  

  Patch Changes

  • 7603248: Fix parsing isolation of individual table cells.
  • f9328cc: Improved block html detection regex to handle certain edge cases that cause extreme slowness. Thank you @ devbrains-com for the basis for this fix 🤝
• 7.4.6 - 2024-04-05
  

  Patch Changes

  • a9e5276: Browsers assign element with id to the global scope using the value as the variable name. E.g.: <h1 id="analytics"> can be referenced via window.analytics.
    This can be a problem when a name conflict happens. For instance, pages that expect analytics.push() to be a function will stop working if the an element with an id of analytics exists in the page.

    In this change, we export the slugify function so that users can easily augment it.
    This can be used to avoid variable name conflicts by giving the element a different id.

    import { slugify } from 'markdown-to-jsx';

    options={{
    slugify: str => {
    let result = slugify(str)

    <span class="pl-k">return</span> <span class="pl-s1">result</span> ? <span class="pl-s">'-'</span> <span class="pl-c1">+</span> <span class="pl-s1">str</span> : <span class="pl-s1">result</span><span class="pl-kos">;</span>
    

    }
    }}

• 7.4.5 - 2024-03-22
  

  Patch Changes

  • f5a0079: fix: double newline between consecutive blockquote syntax creates separate blockquotes

    Previously, for consecutive blockquotes they were rendered as one:

    Input

    > Block A.1
    > Block A.2
    
    > Block B.1

    Output

    <blockquote>
      <p>Block A.1</p>
      <p>Block A.2</p>
      <p>Block.B.1</p>
    </blockquote>

    This is not compliant with the GFM spec which states that consecutive blocks should be created if there is a blank line between them.

• 7.4.4 - 2024-03-21
  

  What's Changed

  • Brackets in link text by @ zegl in #551
  • Multiline footnotes by @ zegl in #553
  • fix: multi-line emphasis by @ austingreco in #550
  • fix: gracefully handle missing image references by @ quantizor in #554
  • chore: add changesets by @ quantizor in #555
  • fix: handle newlines inside HTML tag brackets by @ quantizor in #557
  • fix: html block regex prefix conflict by @ quantizor in #558
  • Version Packages by @ github-actions in #556

  New Contributors

  • @ zegl made their first contribution in #551
  • @ austingreco made their first contribution in #550
  • @ github-actions made their first contribution in #556

  Full Changelog: v7.4.3...v7.4.4

• 7.4.3 - 2024-03-13
  

  What's Changed

  • fix: restore x-browser stable sort logic in #548 (fixes unclosed HTML tags that showed up for some edge cases)

  Full Changelog: v7.4.2...v7.4.3

• 7.4.2 - 2024-03-12
  

  Re-release 7.4.1 with less existential console screaming

• 7.4.1 - 2024-01-29
  

  What's Changed

  • Update README.md by @ majman in #534
  • Automatically strip YAML front matter by @ varnerac in #538

  New Contributors

  • @ majman made their first contribution in #534
  • @ varnerac made their first contribution in #538

  Full Changelog: v7.4.0...v7.4.1

• 7.4.0 - 2024-01-01
  

  Happy New Year! 🎆

  markdown-to-jsx v7.4 features a new option renderRule! — From the README:

  Supply your own rendering function that can selectively override how rules are rendered (note, this is different than options.overrides which operates at the HTML tag level and is more general). You can use this functionality to do pretty much anything with an established AST node; here's an example of selectively overriding the "codeBlock" rule to process LaTeX syntax using the @ matejmazur/react-katex library:

  import { Markdown, RuleType } from 'markdown-to-jsx'
  import TeX from '@ matejmazur/react-katex'

  const exampleContent =
  'Some important formula:\n\nlatex\nmathbb{N} = { a in mathbb{Z} : a > 0 }\n\n'

  function App() {
  return (
  <Markdown
  children={exampleContent}
  options={{
  renderRule(next, node, renderChildren, state) {
  if (node.type === RuleType.codeBlock && node.lang === 'latex') {
  return (
  <TeX as="div" key={state.key}>{String.raw<span class="pl-s1"><span class="pl-kos">${</span><span class="pl-s1">node</span><span class="pl-kos">.</span><span class="pl-c1">text</span><span class="pl-kos">}</span></span>}</TeX>
  )
  }

        <span class="pl-k">return</span> <span class="pl-en">next</span><span class="pl-kos">(</span><span class="pl-kos">)</span>
      <span class="pl-kos">}</span><span class="pl-kos">,</span>
    <span class="pl-kos">}</span><span class="pl-kos">}</span>
  <span class="pl-c1">/</span><span class="pl-c1">&gt;</span>
  

  )
  }

  The README docs around syntax highlighting have also been updated with sample code.

  With the new year comes a push toward v8. Performance will be a top priority, reducing the complexity of the library's regexes to increase throughput for SSR use-cases and ideally eliminate rare but frustrating issues like catastrophic backtracking. In addition, the library will be pivoting into more of a pure compiler model, with a React adapter offered and ones added for other major frameworks as well. The idea is anywhere you can run JS, you can use [secret new library name].

  Stay tuned and thanks for being part of the journey ✌🏼
  Here's to a great 2024 🍾

  markdown-to-jsx is maintained by @ quantizor, buy him a coffee

  Full Changelog: v7.3.2...v7.4.0

• 7.3.2 - 2023-08-05
  

  fix(types): path to esm types in "exports"

  Full Changelog: v7.3.1...v7.3.2

from markdown-to-jsx GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
syofyan-profile	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 17, 2024 7:27am