-
-
Notifications
You must be signed in to change notification settings - Fork 594
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
When formatting the vue file, the template lang='pug'
node will be cleared.
#2460
Comments
@yoyo930021 I installed version 0.30.1, but this problem still exists. |
If you restart? |
This problem still exists in my workspace : But formatting after creating a new directory to test it, is normal : |
What is your .prettierrc file content? |
The
|
@yoyo930021 Before installation, I uninstalled this extension and deleted the So I using the Install from VSIX command in the Extensions view command drop-down, And completed the installation of the Vetur extension. But this problem still exists. |
Can you provide your project or any repro project? If none of these, |
I tried to clone the project on another device, but this problem did not occur. After trying for a while, I found that setting This is a minimal repro case: https://github.com/richex-cn/repro-vetur-formatting-bug-issue-2460 |
I just started experiencing this issue after all formatting was working correctly all day. Suddenly on save now it's deleting the contents of I can confirm that downgrading to vetur 0.29.1 fixes the issue and deletion no longer occurs during save/format. This indicates the problem was introduced with the later vetur versions & releases. |
@IvanCaceres You can try the way I mentioned above, if you still can't solve it, you can communicate with @yoyo930021 . |
Reason: #2347 (comment) |
Ha, I found the problem. In next version, vetur use bundled prettier in this case. |
Vetur: Restart VLS
Info
Problem
No output from the Vue Language Server output panel.
After falling back to 0.29.1, the problem no longer occurs.
The text was updated successfully, but these errors were encountered: