Cannot find module 'lodash' after extension upgrade

[octref]

Vetur also uses lodash and this has been reported many times: https://github.com/vuejs/vetur/issues?utf8=%E2%9C%93&q=is%3Aissue+lodash+is%3Aclosed+

Earliest report is vuejs/vetur#251 at 1.13.1.

So today I'm seeing this error in dev console, and Vim is not loading.
VS Code Insider: 3fec610
macOS 10.12.6.

/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:257 [Extension Host]% Object (at Object.writeFile (/Users/pine/.vscode-insiders/extensions/Equinusocio.vsc-material-theme-1.4.2/extensions/helpers/fs.js:98:13))
/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:257 [Extension Host] Activating extension 'vscodevim.vim' failed: Cannot find module 'lodash'. (at Object.showMessage (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:690:704))
t.log @ /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:257
/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:257 [Extension Host] Activating extension `vscodevim.vim` failed:  Cannot find module 'lodash' (at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:453:87)
t.log @ /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:257
/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:257 [Extension Host] Here is the error stack:  Error: Cannot find module 'lodash'
	at Function.Module._resolveFilename (module.js:470:15)
	at Function.Module._load (module.js:418:25)
	at Function.o._load (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:671:712)
	at Module.require (module.js:498:17)
	at Module.patchedRequire [as require] (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/git/node_modules/diagnostic-channel/dist/src/patchRequire.js:14:46)
	at require (internal/module.js:20:19)
	at Object.<anonymous> (/Users/pine/.vscode-insiders/extensions/vscodevim.vim-0.11.0/out/src/taskQueue.js:11:11)
	at Object.<anonymous> (/Users/pine/.vscode-insiders/extensions/vscodevim.vim-0.11.0/out/src/taskQueue.js:85:3)
	at Module._compile (module.js:571:32)
	at Object.Module._extensions..js (module.js:580:10)
	at Module.load (module.js:488:32)
	at tryModuleLoad (module.js:447:12)
	at Function.Module._load (module.js:439:3)
	at Function.o._load (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:671:712)
	at Module.require (module.js:498:17)
	at Module.patchedRequire [as require] (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/git/node_modules/diagnostic-channel/dist/src/patchRequire.js:14:46) (at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:453:155)
/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:2839 Activating extension 'vscodevim.vim' failed: Cannot find module 'lodash'.
O._logMessageInConsole @ /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:2839

Vim is reporting 0.11.0. And I could find the lodash dependency installed correctly at /Users/pine/.vscode/extensions/vscodevim.vim-0.11.0/node_modules/lodash.

@sandy081 I'll be up early so let me know if you want to debug through this together.
@joaomoreno Does the patchedRequire give you any hint as to why this might happen?

[egamma]

@octref can you check whether the extension is fully installed. This reminds me to issue #43813.

[sandy081]

Yes this is a duplicate of #43813

[vscodebot]

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!