Skip to content

chore: add vite plugin npm support metadata#229

Open
wowsofine wants to merge 1 commit into
MMF-FE:masterfrom
wowsofine:codex/add-vite-plugin-svgicon-metadata
Open

chore: add vite plugin npm support metadata#229
wowsofine wants to merge 1 commit into
MMF-FE:masterfrom
wowsofine:codex/add-vite-plugin-svgicon-metadata

Conversation

@wowsofine

Copy link
Copy Markdown

What changed

Added npm support metadata to packages/vite-plugin-svgicon/package.json:

  • repository points to this GitHub repository.
  • bugs.url points to this repository's issue tracker.

Why

The published vite-plugin-svgicon@2.1.2 npm metadata currently exposes homepage, but omits the standard repository and bugs fields. The package already lives in this repository, and sibling packages in the monorepo use the same metadata shape.

Validation

  • npm view vite-plugin-svgicon@2.1.2 name version homepage repository bugs deprecated dist.tarball scripts --json
  • red metadata smoke before the patch confirmed missing repository and bugs.url
  • metadata smoke after the patch passed
  • npm pack --dry-run --ignore-scripts ./packages/vite-plugin-svgicon
  • npm install --workspaces=false --ignore-scripts --package-lock=false --legacy-peer-deps in packages/vite-plugin-svgicon
  • npm run build in packages/vite-plugin-svgicon
  • post-build npm pack --dry-run --ignore-scripts ./packages/vite-plugin-svgicon
  • git diff --check

Notes: the root yarn install --immutable currently reports existing lockfile drift for workspace dependency ranges and existing peer warnings, so I kept validation focused on the target package surface and did not change the lockfile.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant