Prettier-vscode: Unable to install extension version 0.19.0

Created on 5 Jun 2017 · 14Comments · Source: prettier/prettier-vscode

Upgrading to the latest version of the extension seems to have uninstalled the extension, and trying to re-install the extension from the marketplace does nothing – the "Install" button changes to "Installing" for a few seconds, and then gets reverted back to "Install". Restarting VSCode does not fix the problem.

If there's some way to enable debug logging for extension installation, I can add the logs here.

bug locked

Source

vsaarinen

Most helpful comment

The developer tools' console had an error which said: "An unknown error occurred. Please see the log."

The ~/.vscode/extenstions folder had an esbenp.prettier-vscode-0.19.0 folder in it that only contained node_modules. I removed the esbenp.prettier-vscode-0.19.0 folder, tried reinstalling the extension, and now it went through ok. The problem is now resolved for me – let's hope that it's a freak occurrence that doesn't happen to others.

vsaarinen on 5 Jun 2017

👍4

All 14 comments

Maybe toggle developer tool.
It may be worth looking into ´.vscode/extensions/´

CiGit on 5 Jun 2017

The developer tools' console had an error which said: "An unknown error occurred. Please see the log."

vsaarinen on 5 Jun 2017

👍4

Great you fixed it. It would be great if you could find the logs tho

CiGit on 5 Jun 2017

Do you have any idea where the logs are located? I can't find anything under ~/.vscode.

vsaarinen on 5 Jun 2017

Sadly .... I've no idea...

CiGit on 5 Jun 2017

Having the same issue, haven't resolve it yet. I've tried installing from the command-line and I'm seeing several "self signed cert" errors (I'm running through a proxy). Strict SSL is off, so it should work fine (other extensions are fine).

joewood on 5 Jun 2017

Not sure if this helps, but the install fails on vscode with this:

[ { Error: ENOENT: no such file or directory, open 'f:\vscode\extensions\esbenp.prettier-vscode-0.19.0\package.json'
    errno: -4058,
    code: 'ENOENT',
    syscall: 'open',
    path: 'f:\\vscode\\extensions\\esbenp.prettier-vscode-0.19.0\\package.json' } ]

I use an alternative extensions dir (specified in the command line).

joewood on 5 Jun 2017

I ended up resolving this by using a non-network drive as the alternative extensions dir. Not sure why this extension is sensitive to that.

joewood on 5 Jun 2017

I've a strange feeling. I think it's one of the rare release I've built on Windows ... (WSL)

CiGit on 5 Jun 2017

Same issue just happened here too on mac. @vsaarinen your solution solved it for me!