Use LazyBarrel to improve IDE performance

🔍 Search Terms

"re-export", "barrel file", "optimization", "performance"

✅ Viability Checklist

• 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 isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
• This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion

Can the Typescript Language Server implement and use its own version of the LazyBarrel optimization as an experimental feature to improve IDE performance?

📃 Motivating Example

This feature should improve IDE performance (e.g. type highlight) and reduce the impact of barrel files on Typescript codebases.

Explanation provided on LazyBarrel.

💻 Use Cases

1. What do you want to use this for?

Improving IDE performance.

2. What shortcomings exist with current approaches?

Barrel files have a significant impact on IDE performance in Typescript codebases.

3. What workarounds are you using in the meantime?

Manually de-barreling packages.

Commencez par le TypeScript Language Server et l’explication LazyBarrel liée afin de comprendre l’optimisation proposée et sa portée. Identifiez un point d’intégration expérimental et un scénario mesurable de performance de l’IDE ; la réalisation doit démontrer une amélioration des performances pour du code TypeScript utilisant intensivement les barrels, sans modifier le comportement à l’exécution.