Vscode: Now, Jade has been renamed to Pug

Created on 16 Apr 2016 · 6Comments · Source: microsoft/vscode

VSCode Version: 1.0.0
OS Version: Windows 10

Steps to Reproduce:

Open any pug file without syntax highlighting

Unfortunately, Jade has been renamed to Pug (ref: https://github.com/pugjs/pug/issues/2184).
We should change jade to pug on all documents, extensions and supports...

Do you have any plans?

Source

mizunashi-mana

Most helpful comment

P.S. I left a solution regarding syntax highlighting on this issue for all vscode and pug user.

Add your User settings (Command Palette -> Preferences: Open User Settings -> edit settings.json) such as:

"files.associations": {
  "*.pug": "jade"
}

mizunashi-mana on 16 Apr 2016

👍5

All 6 comments

P.S. I left a solution regarding syntax highlighting on this issue for all vscode and pug user.

Add your User settings (Command Palette -> Preferences: Open User Settings -> edit settings.json) such as:

"files.associations": {
  "*.pug": "jade"
}

mizunashi-mana on 16 Apr 2016

👍5

@gregvanl can you update the doc accordingly.
@aeschli I suggest we support both the .pug and .jade file associations.

egamma on 17 Apr 2016

Definitely keep supporting the now-legacy .jade associations, there is a lot of code floating around still including the old jade, in fact depending on generator versions people use (thinking about express-generator here, possibly others as well), there might actually be new projects coming up using the old jade for quite some time.

bgse on 17 Apr 2016

added the '.pug' file association
once the new name is established and e.g. the pug-lang.com website is up and ready, we can also rename the extension, the label and the language id.