Skip to content

fix(deps): update dependency remove-markdown to v0.6.4#1830

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/remove-markdown-0.6.x
Open

fix(deps): update dependency remove-markdown to v0.6.4#1830
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/remove-markdown-0.6.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 22, 2026

This PR contains the following updates:

Package Change Age Confidence
remove-markdown 0.6.30.6.4 age confidence

Release Notes

zuchka/remove-markdown (remove-markdown)

v0.6.4

Compare Source

Fixes
Improvements
  • Add throwError to TypeScript typings and README
  • Scope published files to reduce package size
Dependencies
  • Bump minimatch 5.1.6 → 5.1.9 (#​110)
  • Bump picomatch 2.3.1 → 2.3.2 (#​109)
  • Bump js-yaml 4.1.0 → 4.1.1 (#​102)

Closes #​111


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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 added the dependencies Pull requests that update a dependency file label May 22, 2026
@safedep
Copy link
Copy Markdown

safedep Bot commented May 22, 2026

SafeDep Report Summary

Green Malicious Packages Badge Green Vulnerable Packages Badge Green Risky License Badge

Package Details
Package Malware Vulnerability Risky License Report
icon remove-markdown @ 0.6.4
pnpm-lock.yaml
ok icon
ok icon
ok icon
🔗

View complete scan results →

This report is generated by SafeDep Github App

@github-actions
Copy link
Copy Markdown

📦 Next.js Bundle Analysis for kami

This analysis was generated by the Next.js Bundle Analysis action. 🤖

Eight Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load % of Budget (350 KB)
/[locale]/[page] 51.23 KB 273.14 KB 78.04% (+/- <0.01%)
/[locale]/friends 55.97 KB 277.88 KB 79.39% (+/- <0.01%)
/[locale]/notes/[id] 75.22 KB 297.13 KB 84.89% (+/- <0.01%)
/[locale]/posts 26.6 KB 248.51 KB 71.00% (🟡 +0.01%)
/[locale]/posts/[category]/[slug] 84.39 KB 306.3 KB 87.51% (+/- <0.01%)
/[locale]/preview 59.78 KB 281.69 KB 80.48% (+/- <0.01%)
/[locale]/projects/[id] 50.39 KB 272.3 KB 77.80% (+/- <0.01%)
/[locale]/recently 100.24 KB 322.15 KB 92.04% (+/- <0.01%)
Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.

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

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants