Search Terms
compilerOptions Lib, autofix Lib, auto Lib generation, Auto compilerOptions
Suggestion
Suggest adding the appropriate library to compilerOptions.lib if you are using a feature that requires it.
Use Cases
- Help the developer code by preventing them from having to look up which compilerOptions.lib setting they need to use a particual feature of the standard library. As it is difficult to remember which version of ES introduced which additions.
- In the future this could be used to auto generate the compilerOptions.Lib the developer needs by the JS features they are using. Which would remove some configuration. 🎉
Examples
Object.entities(object).map(([key, value]) => {
...
});
📎💬 “Looks like your using Object.entities, would you like to add 'es2017.object' to your compilerOptions.lib?”
if (array.includes(testValue)) {
...
}
📎💬 “Looks like your using Array.include, would you like to add 'es2016.array.include' to your compilerOptions.lib?”
Checklist
My suggestion meets these guidelines:
Search Terms
compilerOptions Lib, autofix Lib, auto Lib generation, Auto compilerOptions
Suggestion
Suggest adding the appropriate library to compilerOptions.lib if you are using a feature that requires it.
Use Cases
Examples
📎💬 “Looks like your using Object.entities, would you like to add 'es2017.object' to your compilerOptions.lib?”
📎💬 “Looks like your using Array.include, would you like to add 'es2016.array.include' to your compilerOptions.lib?”
Checklist
My suggestion meets these guidelines: