4 ms·
> JavaScript improvements: IntelliSense for paths in import Does that mean we don't need those extensions anymore? - Path Intellisense: https://marketplace.vi
by ggregoire 10y ago
> JavaScript improvements: IntelliSense for paths in import
Does that mean we don't need those extensions anymore?
- Path Intellisense: https://marketplace.visualstudio.com/items?itemName=christian-kohler.path-intellisense https://marketplace.visualstudio.com/items?itemName=christia...
- NPM Intellisense: https://marketplace.visualstudio.com/items?itemName=christian-kohler.npm-intellisense https://marketplace.visualstudio.com/items?itemName=christia...
(I have not updated yet)
- mattbierner 10y agoIt depends on what you need. The new built-in path intellisense only applies to JavaScript and TypeScript files for require or import statements. The path intellisense extension specifically is much more general and offers additional functionality that you may find helpful. I work on the VSCode team on JS and TS support, so please let us know if you run into any problems with the new path intellisense feature or have ideas on how it could be improved. Thanks
- ggregoire 10y agoThanks for the info. :)
- ggregoire 10y agoHey! I just tried the feature and I've an issue: Intellisense suggests everything, not only paths. e.g. if I start typing './c', it suggests me every symbol in the current file starting with 'c'. I would love to have only the paths available in the project (like the "Path Intellisense" extension does). I will post my feedback on GitHub, in case you don't see this message. :)