Both Emmet and Scaffold Snippets not working

[carstev]

• I have searched through existing issues
• I have read through docs
• I have read FAQ

Info

• Platform: Ubuntu 18.04
• Vetur version: 0.21.0
• VS Code version: 1.35.0 (vscodium)

Problem

Typing scaffold into a new Vue file does nothing. No IntelliSense, no expanding.

Also, Emmet is not working inside <template> unless this option is set:

"emmet.includeLanguages": {
  "vue": "html"
}

Reproducible Case

1. Fresh installation of vscode/vscodium.
2. Install Vetur.
3. Create a new file, select type as Vue.
4. Try some Snippets. In my case scaffold and h1 inside <template>.
5. Both are not recognized.

Yes, not much of an info. Could I do anything to help debug this?

[yoyo930021]

#780 (comment)

[octref]

I cannot repro:

[borekl]

@bdrtsky Vetur works just fine on Linux Mint for me.

[bdrtsky]

Then maybe it's Ubuntu-specific issue? This can't be coincidence, that on both - 18.04 and 16.04 it's not working (in my case even on fresh system). Only highlighting is working for me. I tried to migrate to VSCode, but without Vetur it doesn't make sense...

[octref]

@bdrtsky Are you using https://github.com/VSCodium/vscodium as well? I think it might be an issue from it.

Also see https://github.com/vuejs/vetur/blob/master/docs/FAQ.md#no-syntax-highlighting--no-language-features-working. Sometimes VS Code has corrupted installs of Vetur. The safest way is to download the VSIX, rm -rf ~/.vscode/extensions/octref.vetur-* and use code --install-extension <extension-id | path-to-vsix>.

[bdrtsky]

@octref nope, I am using VSCode downloaded and installed from official Microsoft site.

Just tried to install from VSIX. No changes:

[octref]

@bdrtsky Any error you see in Output -> Vue Language Server?

Do you have any vue related settings such as files.associations that mark Vue files as another type? Also, any other Vue extensions than Vetur?

[bdrtsky]

I don't have any other extensions beside Vetur at all. My settings.json empty.

And yes, I have lot's of error in Output!

[bdrtsky]

Any ideas what could cause those errors? I have absolutely clean installation, deb package downloaded from official site, the only extension installed is by your instructions, no settings modifications made. I didn't use VSCode before much, so I have no idea how to debug it. Didn't expect this could happen with official extension and most popular Linux distro.

[octref]

@bdrtsky You need to open a folder for Vetur to work, as it resolves dependencies from local node_modules:

[bdrtsky]

@octref yes, you right, thank you! It's working just fine, lol. I guess I worked with Sublime too much and didn't even expect such behavior. Sorry for disturbing.

[Yuliang-Lee]

not work for me too

[Dkenny101]

Version 0.22.0 is not working for me also, rolled back to 0.21.1 any everything working as normal again.

[rochabianca]

Same thing for me on Vetur 0.22.0 on macOS, using scaffold simple does not work anymore

[kkost9]

plus one on Vetur 0.22.0 - windows 10

[octref]

See #1386 (comment).

[chadsparrow]

+1 on the same issue and confirm that rolling back to 0.21.1 fixed the issue

[rochabianca]

Apparently on the new versions you have to use "vue" instead of "scaffold"

[dave2k2]

If I substitue and use "vue" it generates: var vm = new Vue({ el: "#replace" }) instead of the usual <template>...</template><script>...</script><style>...</style>

Based on @octref comment above it seems scaffold is gone and the replacement is to individually use "template", "script" and "style".

[wmpedersen]

"vue" creates the template scaffold for me with Vetur 0.22.2 on Windows 10, vscode 1.37.1

[rochabianca]

@dave2k2 If the "vue" command is not working for you, you can bring back the scaffold by creating a personal snippet for it. If you use vscode, go to Code>Preferences>User Snippets, type vue on the input that will show up and paste this code there:

https://gist.github.com/rochabianca/2c39f611b28dfb51f0fb3ff483afbf51

I made some minor changes, like init the template with a div with the name of the file and already put the name too on the script but you can remove this changes by removing the lines 6 and 11

[dave2k2]

@rochabianca that's pretty awesome thanks...actually it's even better!

[rochabianca]

@dave2k2 thank you :DD

[davidtowoju]

Type <vue> and it works

[zeroidentidad]

as @davexpression and @rochabianca said scaffold was replaced by type <vue

[NicholasMunson]

According to the updated documentation @zeroidentidad @davexpression and @rochabianca are all correct <vue will work however, simply writing vue will not work without the < first. One other option is to start with the word default; def has done the trick for me.

[genialkartik]

If you're on Debian Linux and using VS Code, you might not get Scoffold Snippets instead type <vue> and hit enter, and it all works.

[lyqht]

For those who are facing the Emmet problem in visual studio code, add this in your settings.json and it should work 😄

"emmet.includeLanguages": {
        "javascript": "javascriptreact",
        "vue-html": "html",
        "vue": "html",
    }
}

[PedroPauloML]

Apparently on the new versions you have to use "vue" instead of "scaffold"

In my case, the intellisense for snippet is <vue> or .vue. Look this:

[seanfarmar]

Why is this issue closed?
I didn't see a real resolution to this issue?

[rochabianca]

@seanfarmar It's because the scaffold changed its name for vue (don't know about the emmet problem through) so it shouldn't work if you type scaffold. But if you want that back, you can use my gist, here

[ncdorbi]

Try default
It will definitely work

[marciofmjr]

Type <vue> and it works

you are a God, tks!!!

[fadoo-dev]

Apparently on the new versions you have to use "vue" instead of "scaffold"

That was a great help.. thanks alot <3

[emfluenceindia]

Apparently on the new versions you have to use "vue" instead of "scaffold"

"THE" answer!