Uh oh!
There was an error while loading. Please reload this page.
This repository was archived by the owner on Apr 6, 2023. It is now read-only.
Conversation
|
@harlan-zw is attempting to deploy a commit to the Nuxt Team on Vercel. A member of the Team first needs to authorize it. |
vue-metadanielroe
approved these changes
Dec 10, 2022
vue-metavue-meta for head supportpi0
commented
Dec 12, 2022
Member
Thanks! |
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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
❓ Type of change
📚 Description
Originally it seemed like multiple head providers were going to be supported, however with the 3.0 release it seems safe to presume that vue-meta won't be supported in the core anytime soon.
This PR removes vue-meta code, it doesn't introduce any breaking changes (afaik) as there was no way to actually switch to using vue-meta.
📝 Checklist