feat: scan nested subfolders for custom collections#407
Merged
Conversation
antfu
reviewed
Jun 27, 2025
Member
antfu
left a comment
There was a problem hiding this comment.
I think we should have an option to toggle this behavour, as nested might not always be desired in every project.
Contributor
Author
|
Agreed, I’ve implemented a parameter to support this behavior |
76d4358 to
11fffa9
Compare
antfu
approved these changes
Oct 22, 2025
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
2 participants
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.
🔗 Linked issue
#374 - Recursive search in customCollections directories
❓ Type of change
📚 Description
Added an enhancement to the
@nuxt/iconlibrary that enables scanning of nested subfolders for custom SVG icon collections. Icons located in paths likepath/to/icon.svgare now automatically included in the bundle with the namepath-to-icon. This expands the ability to work with deeply nested folder structures, simplifying the organization and use of custom icons.Why is this change necessary?
Previously, the library only supported icons in the root folder of a collection, limiting file organization. This enhancement makes the structure more flexible, allowing developers to use nested folders without needing to create flat icon names like
arrow-right-line.svgorarrow-right-outline.svg.What problem does it solve?
Removes the limitation of scanning only the root folder, improving UX for developers working with custom icon collections in complex project structures.