Skip to content

fix: explicitly set object plugin types#329

Closed
OrkhanAlikhanov wants to merge 1 commit into
vuetifyjs:mainfrom
OrkhanAlikhanov:fix/explicit-plugin-types
Closed

fix: explicitly set object plugin types#329
OrkhanAlikhanov wants to merge 1 commit into
vuetifyjs:mainfrom
OrkhanAlikhanov:fix/explicit-plugin-types

Conversation

@OrkhanAlikhanov

Copy link
Copy Markdown

Description

Fixed type generation for object plugins

Linked Issues

Fixes #328

Additional Context


Tip

The author of this PR can publish a preview release by commenting /publish below.

@OrkhanAlikhanov OrkhanAlikhanov changed the title Explicitly set object plugin types fix: explicitly set object plugin types Jul 24, 2025
@OrkhanAlikhanov

Copy link
Copy Markdown
Author

@userquin can you please have a look?

@AndreyYolkin AndreyYolkin added bug Something isn't working area: types TypeScript types needs rebase Has merge conflicts; needs rebase on base branch labels Jun 6, 2026
@AndreyYolkin

Copy link
Copy Markdown
Contributor

Verified this is no longer needed. After the monorepo refactor, runtime plugins ship as raw .ts, so defineNuxtPlugin({...}) already infers Plugin<T> & ObjectPlugin<T> (not any), and Nuxt 4's generated InjectionType fallback is now unknown (harmless in the intersection: X & unknown = X). Confirmed via typecheck that the vuetify-icons plugin type resolves concretely rather than to any. Closing as resolved — thanks for the investigation that pinpointed the root cause in #328.

@OrkhanAlikhanov OrkhanAlikhanov deleted the fix/explicit-plugin-types branch June 6, 2026 20:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: types TypeScript types bug Something isn't working needs rebase Has merge conflicts; needs rebase on base branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

vuetify-icons runtime plugin breaks nuxt injections

2 participants