Public repository URL
https://github.com/vbenjs/vite-plugin-svg-icons
Upstream issue URL, if any
No upstream issue found. I opened an upstream PR with the package metadata fix:
vbenjs/vite-plugin-svg-icons#125
Bug or task summary
Package: vite-plugin-svg-icons@2.0.1
The published npm package metadata has a malformed bugs.url:
https://github.com/anncwb/vite-plugin-svg-i cons/issues
The repository slug contains a stray space, so npm consumers following the package issue tracker link do not reach the intended GitHub issues page.
Expected behavior: bugs.url should point to the package issue tracker:
https://github.com/anncwb/vite-plugin-svg-icons/issues
Actual behavior: bugs.url points to the malformed svg-i cons path.
Why this is likely small: the upstream PR changes only packages/core/package.json and corrects a single metadata URL. Runtime code paths are unchanged.
Exact reproduction commands
node -e "fetch('https://registry.npmjs.org/vite-plugin-svg-icons/2.0.1').then(r=>r.json()).then(j=>console.log(JSON.stringify({name:j.name,version:j.version,repository:j.repository,bugs:j.bugs,homepage:j.homepage},null,2)))"
Observed metadata includes:
bugs.url = https://github.com/anncwb/vite-plugin-svg-i cons/issues
File/function/test pointers
Verification performed on the fixed checkout
node -e "const fs=require('fs'); const p='packages/core/package.json'; const j=JSON.parse(fs.readFileSync(p,'utf8')); console.log(JSON.stringify({bugs:j.bugs,repository:j.repository,homepage:j.homepage},null,2));"
git diff --check
The parsed package metadata now reports:
bugs.url = https://github.com/anncwb/vite-plugin-svg-icons/issues
Environment notes
- Verified on 2026-06-10.
- Windows PowerShell.
- Node fetch against npm registry.
- Package version checked:
vite-plugin-svg-icons@2.0.1.
- Upstream default branch checked:
vbenjs/vite-plugin-svg-icons@main.
Duplicate or active-work check
Before submitting, I checked:
- Charles microbounty issues for
vite-plugin-svg-icons and the malformed svg-i cons string.
- Upstream issues and PRs for
bugs metadata / package metadata.
No visible duplicate Charles issue, upstream issue, or upstream PR was found before opening vbenjs/vite-plugin-svg-icons#125.
Rule check
Payout details can be provided after selection.
Public repository URL
https://github.com/vbenjs/vite-plugin-svg-icons
Upstream issue URL, if any
No upstream issue found. I opened an upstream PR with the package metadata fix:
vbenjs/vite-plugin-svg-icons#125
Bug or task summary
Package:
vite-plugin-svg-icons@2.0.1The published npm package metadata has a malformed
bugs.url:The repository slug contains a stray space, so npm consumers following the package issue tracker link do not reach the intended GitHub issues page.
Expected behavior:
bugs.urlshould point to the package issue tracker:Actual behavior:
bugs.urlpoints to the malformedsvg-i conspath.Why this is likely small: the upstream PR changes only
packages/core/package.jsonand corrects a single metadata URL. Runtime code paths are unchanged.Exact reproduction commands
Observed metadata includes:
File/function/test pointers
packages/core/package.jsonVerification performed on the fixed checkout
The parsed package metadata now reports:
Environment notes
vite-plugin-svg-icons@2.0.1.vbenjs/vite-plugin-svg-icons@main.Duplicate or active-work check
Before submitting, I checked:
vite-plugin-svg-iconsand the malformedsvg-i consstring.bugs metadata/package metadata.No visible duplicate Charles issue, upstream issue, or upstream PR was found before opening vbenjs/vite-plugin-svg-icons#125.
Rule check
Payout details can be provided after selection.