search

aquia-inc / template-vite-react

Vite-powered React template that uses TypeScript and SWC for building highly performant applications. Comes with modern tooling and scripts for building, testing, and developing applications efficiently. Includes authentication support with AWS Cognito and protected routes.
MIT License
2 stars 2 forks source link

build(deps): bump markdown-to-jsx from 7.3.2 to 7.5.0 in the npm_and_yarn group #129

Closed dependabot[bot] closed 2 weeks ago

dependabot[bot] commented 2 weeks ago

Bumps the npm_and_yarn group with 1 update: markdown-to-jsx.

Updates markdown-to-jsx from 7.3.2 to 7.5.0

Release notes

Sourced from markdown-to-jsx's releases.

v7.5.0

Minor Changes

  • 62a16f3: Allow modifying HTML attribute sanitization when options.sanitizer is passed by the composer.

    By default a lightweight URL sanitizer function is provided to avoid common attack vectors that might be placed into the href of an anchor tag, for example. The sanitizer receives the input, the HTML tag being targeted, and the attribute name. The original function is available as a library export called sanitizer.

    This can be overridden and replaced with a custom sanitizer if desired via options.sanitizer:

    // sanitizer in this situation would receive:
// ('javascript:alert("foo")', 'a', 'href')

    <Markdown options={{ sanitizer: (value, tag, attribute) => value }}>
{[foo](https://github.com/quantizor/markdown-to-jsx/blob/HEAD/javascript:alert(&quot;foo&quot;))}
</Markdown>
    

    // or
    

    compiler('foo', {
sanitizer: (value, tag, attribute) => value,
})

Patch Changes

  • 553a175: Replace RuleType enum with an object

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 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)

... (truncated)

Changelog

Sourced from markdown-to-jsx's changelog.

7.5.0

Minor Changes

  • 62a16f3: Allow modifying HTML attribute sanitization when options.sanitizer is passed by the composer.

    By default a lightweight URL sanitizer function is provided to avoid common attack vectors that might be placed into the href of an anchor tag, for example. The sanitizer receives the input, the HTML tag being targeted, and the attribute name. The original function is available as a library export called sanitizer.

    This can be overridden and replaced with a custom sanitizer if desired via options.sanitizer:

    // sanitizer in this situation would receive:
// ('javascript:alert("foo")', 'a', 'href')

    ;<Markdown options={{ sanitizer: (value, tag, attribute) => value }}>
{[foo](https://github.com/quantizor/markdown-to-jsx/blob/main/javascript:alert(&quot;foo&quot;))}
</Markdown>
    

    // or
    

    compiler('foo', {
sanitizer: (value, tag, attribute) => value,
})

Patch Changes

  • 553a175: Replace RuleType enum with an object

7.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 🤝

7.4.6

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={{

... (truncated)

Commits


Dependabot compatibility score

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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/aquia-inc/template-vite-react/network/alerts).