Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Language service support for classic JavaScript patterns meta-issue #40025

Open
2 of 5 tasks
minestarks opened this issue Aug 12, 2020 · 0 comments
Open
2 of 5 tasks

Language service support for classic JavaScript patterns meta-issue #40025

minestarks opened this issue Aug 12, 2020 · 0 comments
Labels
Meta-Issue An issue about the team, or the direction of TypeScript

Comments

@minestarks
Copy link
Member

minestarks commented Aug 12, 2020

One consistent piece of feedback from users who have been using Visual Studio long-term to develop JavaScript-only projects is that the old, execution-based language service in Visual Studio 2015 did a better job picking up certain common JavaScript patterns than the TypeScript language service.

This is a meta-issue to collect specific instances where TypeScript didn't do as good a job as VS 2015 IntelliSense. By targeting these specific fixes we hope to improve the experience of users upgrading from VS 2015, as well as improve our type inference for pure JavaScript in general.

@DanielRosenwasser DanielRosenwasser added the Meta-Issue An issue about the team, or the direction of TypeScript label Aug 12, 2020
@DanielRosenwasser DanielRosenwasser changed the title [meta] Improve pure JavaScript language service support Language service support for classic JavaScript patterns meta-issue Aug 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Meta-Issue An issue about the team, or the direction of TypeScript
Projects
None yet
Development

No branches or pull requests

2 participants