-
-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A error [plugin:vite:vue-jsx] unknown: Unexpected token
occurs during hot reload.
#423
Open
9 tasks done
Labels
p3-minor-bug 🔨
An edge case that only affects very specific usage (priority)
Comments
ipcjs
changed the title
A error
A error Jul 8, 2024
[plugin:vite:vue-jsx] unknown: Unexpected token (4:12)
occurs during hot reload.[plugin:vite:vue-jsx] unknown: Unexpected token
occurs during hot reload.
same problem |
edison1105
added
p4-important ❗
Violate documented behavior or significantly improves performance (priority)
and removed
pending triage
labels
Sep 19, 2024
9 tasks
edison1105
added
p3-minor-bug 🔨
An edge case that only affects very specific usage (priority)
and removed
p4-important ❗
Violate documented behavior or significantly improves performance (priority)
labels
Sep 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related plugins
plugin-vue
plugin-vue-jsx
Describe the bug
Describe
This commit introduced a bug: c891652
When modifying a file containing a type used by
defineProps
, it throws a[plugin:vite:vue-jsx] unknown: Unexpected token (4:12)
error.Analyse
The key line of code should be this:
vite-plugin-vue/packages/plugin-vue/src/handleHotUpdate.ts
Lines 344 to 349 in 7fc7994
It cleared the cache of the
<script>
block, but only reloaded the<script>
block itself without reloading the entire Vue file. As a result, the load method couldn't read the<script>
block.Reproduction
https://github.com/ipcjs/vite-plugin-vue-type-dep-change-bug
Steps to reproduce
pnpm dev
Position.toString()
methodSystem Info
Used Package Manager
pnpm
Logs
Click to expand!
Validations
The text was updated successfully, but these errors were encountered: