chore(repo): Update issue templates and documentation for package ren…#4379
Merged
Conversation
…aming and deprecations
Contributor
There was a problem hiding this comment.
Pull request overview
Cleans up references to renamed/legacy Lucide packages (e.g. lucide-vue-next → @lucide/vue, lucide-svelte → @lucide/svelte, lucide-angular → @lucide/angular) across the issue templates, the labeler config, the Prettier ignore file, and the docs site, and removes the obsolete legacy lucide-angular.md doc.
Changes:
- Refresh affected-package checkbox lists and version placeholder in the bug/feature issue templates.
- Update path globs in
.github/labeler.ymland.prettierignoreto match the newpackages/{vue,svelte,angular}directory layout. - Update
docs/guide/index.mdpackage links to local relative paths, retire the legacylucide-angular.mdpage, and modernize one Vue import example.
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
.github/ISSUE_TEMPLATE/02_bug_report.yml |
Reorganizes affected-package list around new @lucide/* names and updates the version placeholder. |
.github/ISSUE_TEMPLATE/04_feature_request.yml |
Same affected-package list cleanup as the bug template. |
.github/labeler.yml |
Replaces legacy packages/lucide-{vue,vue-next,svelte,angular}/* globs with the new packages/{vue,svelte,angular}/* paths. |
.prettierignore |
Updates ignore paths for the renamed Angular and Svelte packages. |
docs/guide/index.md |
Switches the official-packages paragraph from absolute lucide.dev URLs to local relative paths and drops the separate vue vs vue-next entry. |
docs/guide/packages/lucide-angular.md |
Removes the legacy Angular package documentation page. |
docs/guide/packages/lucide-vue.md |
Adds a blank line and updates one accessibility example import to @lucide/vue. |
Comments suppressed due to low confidence (1)
.github/labeler.yml:73
- The "vue package" labeler rule used to match both
packages/lucide-vue/*(Vue 2 legacy) andpackages/lucide-vue-next/*. Even though the new@lucide/vuepackage now lives underpackages/vue/, the deprecatedlucide-vue-nextpackage is still listed as a supported (deprecated) option in the bug/feature issue templates, suggesting the package still exists for users to file issues against. Ifpackages/lucide-vue-next/(orpackages/lucide-vue/) still ships from this monorepo, removing those globs means PRs touching them will no longer get the vue label. Please verify the legacy package directories are truly gone and, if not, keep their globs in the rule.
💎 vue package:
- changed-files:
- any-glob-to-any-file:
- 'packages/vue/*'
# For changes in the Lucide angular package
🅰️ angular package:
- changed-files:
- any-glob-to-any-file:
- 'packages/angular/*'
# For changes in the Lucide preact package
⚛️ preact package:
- changed-files:
- any-glob-to-any-file:
- 'packages/lucide-preact/*'
# For changes in the Lucide svelte package
🧣 svelte package:
- changed-files:
- any-glob-to-any-file:
- 'packages/svelte/*'
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes