Nowadays, TypeScript's type packages are typically found in node packages with the format @types/packagename
.
Strangely, Visual Studio, despite its support for npm packages, appears to be unable to locate them:
https://i.sstatic.net/7tOK1.png
The solution explorer displays an unexpected output when this happens:
https://i.sstatic.net/qDQ3R.png
It seems like Visual Studio is struggling to properly interpret the package names.
As a result, it is also unable to install the package.
This issue has been observed in the latest Visual Studio 2017, and was similarly present in Visual Studio 2015.
Despite this, there are mentions of others successfully utilizing npm with Visual Studio, suggesting that they are able to use these type packages.
I am working on a new nodejs console application created through the wizard.
What could be causing this problem and how can it be resolved?