This repository was archived by the owner on Apr 6, 2023. It is now read-only.
fix(nuxt): remove literal <script setup> from comment#6331
Merged
Conversation
✅ Deploy Preview for nuxt3-docs canceled.
|
Member
|
Could it be related to one of our internal transforms? |
atinux
approved these changes
Aug 3, 2022
Member
|
Approved as a hotfix (cannot run docus theme locally now), I let you find the root cause 🍀 |
Member
Author
|
Yes, I'm looking into root cause. 👍 |
Member
Author
Member
|
@danielroe Does it mean Nuxt and Vite defaults are safe? |
Member
Author
|
No problem with Nuxt. It was a wrong usage of the SFC parser. |
Merged
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Seems there's a compiler bug (which I will look into) giving this error when using client-only. This PR is a hotfix.
📝 Checklist