feat!: use vue 2.7 composition api #645
Merged
Conversation
This file contains 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
Closed
1 task
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.
This PR updates
@nuxtjs/composition-apito use Vue 2.7 to provide the Composition API rather than using@vue/composition-api. It also drops usage ofunplugin-vue2-script-setupin favour of native<script setup>(but note that this drops support for the experimental reactivity transform).Key points in favour of the change are increased stability and not having to add workarounds to ensure we are using the same Vue instance.
BREAKING CHANGES
Some of the API and behaviour differ between Vue 2.7 and
@vue/composition-api. In addition, there are some composition utilites that are no longer exported from@nuxtjs/composition-api, such asdefineAsyncComponent,warn, etc.Please read https://blog.vuejs.org/posts/vue-2-7-naruto.html for the announcement and more information.
resolves #644, resolves #643, resolves #593, resolves #19