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

Resolutions in tsserver should be shared among projects dependng on module options #53477

Open
5 tasks
sheetalkamat opened this issue Mar 23, 2023 · 0 comments
Open
5 tasks
Assignees
Labels
Domain: Performance Reports of unusually slow behavior Suggestion An idea for TypeScript

Comments

@sheetalkamat
Copy link
Member

Suggestion

πŸ” Search Terms

List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily and help provide feedback.

βœ… Viability Checklist

My suggestion meets these guidelines:

  • This wouldn't be a breaking change in existing TypeScript/JavaScript code
  • This wouldn't change the runtime behavior of existing JavaScript code
  • This could be implemented without emitting different JS based on the types of the expressions
  • This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
  • This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

πŸ“ƒ Motivating Example

πŸ’» Use Cases

Creating issues to track some of the investigations i have been doing so it doesnt slip my mind,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Domain: Performance Reports of unusually slow behavior Suggestion An idea for TypeScript
Projects
None yet
Development

No branches or pull requests

3 participants