Skip to content
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

Emmet HTML slow to recognize #436

Closed
2 tasks done
rjoo opened this issue Sep 20, 2017 · 7 comments
Closed
2 tasks done

Emmet HTML slow to recognize #436

rjoo opened this issue Sep 20, 2017 · 7 comments

Comments

@rjoo
Copy link

rjoo commented Sep 20, 2017

Info

  • Platform: Win
  • Vetur version: 0.9.7
  • VSCode version: 1.16.1 (both 32/64 bit versions)

Problem

Emmet is taking an incredibly long time to recognize html abbreviations in .vue files. The issue is not so bad when there is only a <template> in the file, but when <script> and <style> are present it's practically unusable.

With Emmet CSS abbrs, there's only a slight inconsiderable delay.

I've reinstalled vetur, disabled all other extensions, and also reinstalled VS Code (to test differences between 32/64 bit versions).

Reproducible Case

@octref
Copy link
Member

octref commented Sep 20, 2017

Do you have a repro case? If not does this happen to Veturpack or any vue-cli templates?

@rjoo
Copy link
Author

rjoo commented Sep 20, 2017

This project was created with vue-cli's webpack template. I just tested it with a bare webpack-simple template and saw the same thing happening.

However, I noticed that if I open a new VS Code window that's not tied to any folder, and open a .vue file directly, it is much faster.

@HerringtonDarkholme
Copy link
Member

HerringtonDarkholme commented Sep 21, 2017

You probably need to provide a reproduction project for this issue.

I cannot reproduce it on webpack-simple.

@HerringtonDarkholme
Copy link
Member

I guess this is caused by resolving component options in completion method.

@rjoo
Copy link
Author

rjoo commented Sep 21, 2017

After restarting the laptop today, I got a new error about the 'js-beautify' module not being found. Reinstalling veture again then fixed that problem and the speed problems went away.

I'm not sure what exactly changed from yesterday, other than the restart which would imply the issue was local to my machine's state prior. Will close this issue and sorry for any time wasted.

Thanks for this awesome extension!

@rjoo rjoo closed this as completed Sep 21, 2017
@octref
Copy link
Member

octref commented Sep 21, 2017

Yeah, that's in the FAQ. Sometimes VSCode messes up node_modules while updating. Glad you solved it.

@qpenta
Copy link

qpenta commented Mar 16, 2024

with me its works unistall and disable vetur and use vue - official (volax). Vetur is useless today

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants