refactor!: rename autoImports
to imports
#528
Merged
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
vueuse/vueuse#2176
β Type of change
π Description
This PR is the equivalent of nuxt/framework#6864 for Nuxt Bridge to keep the project in alignment with Nuxt 3.
As this feature now goes beyond just auto-imports, the naming
autoImports
as become a bit confusing and ambiguous. See nuxt/framework#6768 for more. This PR renames Nuxt optionautoImports
toimports
and hooksautoImports:*
toimports:*
. This also aligns withcomponents
option.π Migration
autoImports
named toimports
. HooksautoImports:*
renamed toimports:*
.for
nuxt.config.ts
:for module authors:
π Checklist