fix: wrap nuxt runtime plugin in defineNuxtPlugin#241
Open
ExEr7um wants to merge 1 commit into
Open
Conversation
|
@ExEr7um is attempting to deploy a commit to the Formkit Team on Vercel. A member of the Team first needs to authorize it. |
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
1 participant
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.
Fixes #240
Since v0.10.0 Nuxt prints a warning that the plugin is not wrapped in
defineNuxtPlugin— the wrapper was dropped in eb9285b during the build rework.Turns out it wasn't actually needed for the build: mkdist doesn't resolve imports, so
#importspasses through to the publishedplugin.mjsjust fine. This restores the wrapper and keeps the relative vue import.Tested in
build/nuxt-playgroundwith Nuxt 4.4.8 — warning is gone, directive still registers.