feedback
feedback copied to clipboard
fix(deps): update dependency markdown-to-jsx to v7.4.7
This PR contains the following updates:
Package | Change | Age | Adoption | Passing | Confidence |
---|---|---|---|---|---|
markdown-to-jsx (source) | 7.1.9 -> 7.4.7 |
Release Notes
quantizor/markdown-to-jsx (markdown-to-jsx)
v7.4.7
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 🤝
v7.4.6
Patch Changes
-
a9e5276
: Browsers assign element withid
to the global scope using the value as the variable name. E.g.:<h1 id="analytics">
can be referenced viawindow.analytics
. This can be a problem when a name conflict happens. For instance, pages that expectanalytics.push()
to be a function will stop working if the an element with anid
ofanalytics
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 differentid
.import { slugify } from 'markdown-to-jsx'; options={{ slugify: str => { let result = slugify(str) return result ? '-' + str : result; } }}
v7.4.5
Patch Changes
-
f5a0079
: fix: double newline between consecutive blockquote syntax creates separate blockquotesPreviously, 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.
v7.4.4
Patch Changes
-
8eb8a13
: Handle newlines inside of HTML tags themselves (not just nested children.) -
c72dd31
: Defaultchildren
to an empty string if no content is passed. -
4f752c8
: Fix handling of deeply-nested HTML in some scenarios. -
1486aa4
: Handle extra brackets in links, thanks @​zegl! -
1486aa4
: Allow a newline to appear within inline formatting like bold, emphasis, etc, thanks @​austingreco! -
1486aa4
: Starting using changesets -
fd35402
: Fix HTML block regex for custom component scenarios where a nested component shares the same prefix as the parent, e.g. Accordion vs AccordionItem. -
1486aa4
: Fix support for multi-line footnotes, thanks @​zegl!
v7.4.3
What's Changed
- fix: restore x-browser stable sort logic in https://github.com/quantizor/markdown-to-jsx/pull/548 (fixes unclosed HTML tags that showed up for some edge cases)
Full Changelog: https://github.com/quantizor/markdown-to-jsx/compare/v7.4.2...v7.4.3
v7.4.2
Re-release 7.4.1 with less existential console screaming
v7.4.1
What's Changed
- Update README.md by @​majman in https://github.com/quantizor/markdown-to-jsx/pull/534
- Automatically strip YAML front matter by @​varnerac in https://github.com/quantizor/markdown-to-jsx/pull/538
New Contributors
- @​majman made their first contribution in https://github.com/quantizor/markdown-to-jsx/pull/534
- @​varnerac made their first contribution in https://github.com/quantizor/markdown-to-jsx/pull/538
Full Changelog: https://github.com/quantizor/markdown-to-jsx/compare/v7.4.0...v7.4.1
v7.4.0
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\n```latex\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`${node.text}`}</TeX>
)
}
return next()
},
}}
/>
)
}
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: https://github.com/quantizor/markdown-to-jsx/compare/v7.3.2...v7.4.0
v7.3.2
fix(types): path to esm types in "exports"
Full Changelog: https://github.com/probablyup/markdown-to-jsx/compare/v7.3.1...v7.3.2
v7.3.1
What's Changed
- add dev-time error if trying to provide bad input
Full Changelog: https://github.com/probablyup/markdown-to-jsx/compare/v7.3.0...v7.3.1
v7.3.0
What's Changed
- chore(deps): bump word-wrap from 1.2.3 to 1.2.4 by @​dependabot in https://github.com/probablyup/markdown-to-jsx/pull/505
- chore(deps): bump semver from 6.3.0 to 6.3.1 by @​dependabot in https://github.com/probablyup/markdown-to-jsx/pull/504
- chore(deps): bump tough-cookie from 4.1.2 to 4.1.3 by @​dependabot in https://github.com/probablyup/markdown-to-jsx/pull/503
- #​379 - Allow more custom HTML character codes by @​brianfryer in https://github.com/probablyup/markdown-to-jsx/pull/502
- fix: correctly parse markdown inside of a table row when a preceding column has nested HTML elements by @​gusbmurphy in https://github.com/probablyup/markdown-to-jsx/pull/501
- add option to enforce a space between headings by @​insanicly in https://github.com/probablyup/markdown-to-jsx/pull/440
- fix: Update package.json for "type": "module" with updated
size-limit
tests forindex.cjs
andindex.module.js
(replacingindex.js
) by @​nbarrow-inspire-labs in https://github.com/probablyup/markdown-to-jsx/pull/500
New Contributors
- @​brianfryer made their first contribution in https://github.com/probablyup/markdown-to-jsx/pull/502
- @​gusbmurphy made their first contribution in https://github.com/probablyup/markdown-to-jsx/pull/501
- @​insanicly made their first contribution in https://github.com/probablyup/markdown-to-jsx/pull/440
- @​nbarrow-inspire-labs made their first contribution in https://github.com/probablyup/markdown-to-jsx/pull/500
Full Changelog: https://github.com/probablyup/markdown-to-jsx/compare/v7.2.1...v7.3.0
v7.2.1
What's Changed
- fix: move
types
condition to the front by @​Andarist in https://github.com/probablyup/markdown-to-jsx/pull/492
New Contributors
- @​Andarist made their first contribution in https://github.com/probablyup/markdown-to-jsx/pull/492
Full Changelog: https://github.com/probablyup/markdown-to-jsx/compare/v7.2.0...v7.2.1
v7.2.0
What's Changed
- Resolve issue with catastrophic backtracking regex by @​Prestaul in https://github.com/probablyup/markdown-to-jsx/pull/436
- fix: add package.json to exports by @​ilia-kurganskii in https://github.com/probablyup/markdown-to-jsx/pull/445
- refactor: simplify image+link regexes, allow data image URLs by @​probablyup in https://github.com/probablyup/markdown-to-jsx/pull/472
- Parse link reference definitions surrounded by angle brackets by @​ElliotFriend in https://github.com/probablyup/markdown-to-jsx/pull/476
- feat: add support for "mark" syntax
==text==
by @​probablyup in https://github.com/probablyup/markdown-to-jsx/pull/471 - Syntax nits to make IntelliJ happy by @​ikonst in https://github.com/probablyup/markdown-to-jsx/pull/417
- fix: improve link detection regex by @​probablyup in https://github.com/probablyup/markdown-to-jsx/pull/483
New Contributors
- @​Prestaul made their first contribution in https://github.com/probablyup/markdown-to-jsx/pull/436
- @​ilia-kurganskii made their first contribution in https://github.com/probablyup/markdown-to-jsx/pull/445
- @​ElliotFriend made their first contribution in https://github.com/probablyup/markdown-to-jsx/pull/476
Full Changelog: https://github.com/probablyup/markdown-to-jsx/compare/v7.1.9...v7.2.0
Configuration
đź“… Schedule: Branch creation - "after 2am and before 5am every weekday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
â™» 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.