Cannot activate the extension due to errors

[mgara]

Activating extension 'peakchen90.vue-beautify' failed: vscode.window.showWarningMessage is not a constructor. _logMessageInConsole @ extensionService.ts:790 _logOrShowMessage @ extensionService.ts:804 (anonymous) @ mainThreadExtensionService.ts:67 (anonymous) @ errors.ts:184 n @ errors.ts:184 $onExtensionActivationError @ mainThreadExtensionService.ts:65 _doInvokeHandler @ rpcProtocol.ts:390 _invokeHandler @ rpcProtocol.ts:375 _receiveRequest @ rpcProtocol.ts:295 _receiveOneMessage @ rpcProtocol.ts:225 _protocol.onMessage.e @ rpcProtocol.ts:100 fire @ event.ts:584 r @ ipc.net.ts:332 e @ ipc.net.ts:339 fire @ event.ts:584 e @ ipc.net.ts:157 _socketDataListener.e @ ipc.net.ts:171 emit @ events.js:182 addChunk @ _stream_readable.js:279 readableAddChunk @ _stream_readable.js:264 Readable.push @ _stream_readable.js:219 onread @ net.js:636

[Extension Host] Here is the error stack: TypeError: vscode.window.showWarningMessage is not a constructor at activate (c:\Users\Meher.vscode-insiders\extensions\peakchen90.vue-beautify-2.0.4\extension.js:15:5) at Function._callActivateOptional (c:\Users\Meher\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:701:21) at Function._callActivate (c:\Users\Meher\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:700:704) at define._doActivateExtension.Promise.all.then.e (c:\Users\Meher\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:699:895) (at define._activateExtension.s._host.actualActivateExtension.then.t (c:\Users\Meher\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:442:921))

[liushengyu]

I met the same problem. So is there any solution yet?

[Avi-E-Koenig]

+1 on this, I must note, however, I came across this by accident while debugging something else. As far as I can tell...the plugin works fine, for me anyways.