You can ask, but we can’t deliver. Only MS can do that. Hopefully you submitted your feedback to the VS Code issues repo on GitHub at GitHub · Where software is built
While Visual Studio and other feedback is gathered at the company’s Developer Community site, the open-source-based VS Code is a different animal.
We’ve followed this space for decades and we know that Microsoft does a great job of responding to user requests for dev tooling. It might take years for major features, but they studiously address the big stuff – eventually.
In the meantime, here’s the current state in VS Code as of mid-2025:
Printing Source Code
VS Code doesn’t include a native print feature yet, but the community has filled the gap nicely with extensions like PrintCode, Print (by PD Consulting), and vsc-print, which let you print syntax-highlighted code or rendered Markdown via your browser. If printing source code on paper still matters to you (as it does to many developers!), the best way forward is to post feedback on VS Code’s GitHub repo or user surveys—Microsoft does monitor those.
JavaScript and TypeScript Support
• JavaScript – Fully supported out of the box: IntelliSense, syntax highlighting, debugging (Node.js/browser). Additional tools (like ESLint, Prettier) are just an extension install away.
• TypeScript – Also fully supported with smart editing, refactoring, debugging, and more. VS Code doesn’t include the compiler, so you’ll need to install tsc (globally or per project) to transpile your .ts files. Once set up, you get streamlined workflows like automatic builds, debugging with source maps, and solid tooling support.
Bottom line:
– Printing in VS Code: Not built-in, but feasible via extensions—and you should definitely ask Microsoft directly if you’d like it natively integrated.
– JS/TS support: Both are first-class citizens in VS Code, with full editor and execution support (minus the compiler), and you can run/debug your code right inside the IDE.