Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ERROR > command 'HookyQR.beautifyFile' not found

See original GitHub issue

I have just upgraded to beautify 1.1.0

Operating System (+Version): Windows 10 Build 15063
VS Code Version: 1.12.2
beautify Version: 1.1.0

VS Code:

{
    "workbench.iconTheme": "vscode-icons",
    "workbench.colorTheme": "One Dark Pro",
    "window.zoomLevel": 0,
    "html.format.wrapAttributes": "force-aligned",
    "editor.fontFamily": "Consolas, 'Courier New', monospace",
    "editor.tabSize": 2,
    "workbench.sideBar.location": "right"
}

.jsbeautifyrc

{
  "wrap_attributes": "force-aligned"
}

.editorconfig

root = true

[*]
charset = utf-8
indent_style = space
indent_size = 2
insert_final_newline = true
trim_trailing_whitespace = true

[*.md]
max_line_length = off
trim_trailing_whitespace = false

Action performed

Format any file with HookyQR.beautifyFile command F1 > Beautify file

Expected results

Expected formatted document

Actual results

ERROR > command ‘HookyQR.beautifyFile’ not found

Extra dumb question not related to the issue

Whenever I ALT+SHIFT+F, the file is not formated using .jsbeautifyrc configuration. Is this expected behavior? Since it appears that ALT+SHIFT+F command formats the document using VSCodeBeautify.

Issue Analytics

State:
Created 6 years ago
Reactions:4
Comments:9 (1 by maintainers)

Top GitHub Comments

9reactions

vdurantecommented, May 31, 2017

@steven11329 @maeganjwilson

Apparently I solved it by going to %USERPROFILE%\.vscode\extensions\HookyQR.beautify-1.1.0 in a command prompt and running npm install --production. Then I went to vscode and hit F1 > Reload Window

EDIT > at first, reload window didn’t work. I just took some time to grab a coffee, restart vscode and bang my head to the wall. When I came back it was magically working.

4reactions

HookyQRcommented, May 31, 2017

Fixed in 1.1.1. I really have to track down and remove that old version of VSCE that my laptop keeps finding. 😞 Sorry everyone.