Hey maintainers,

A few days ago, while I was working on One Double Zero, I noticed that running the version command of the application was very slow - somewhere around half a second to get the version of the application output to the console.

After investigating, I discovered that importing AST_NODE_TYPES from @typescript-eslint/typescript-estree was very slow - something around 350ms just to execute import {AST_NODE_TYPES} from "@typescript-eslint/typescript-estree"; at runtime. After digging into the source code of the package, I discovered that @typescript-eslint/typescript-estree, at some point, import the whole typescript package before it is needed - i.e. typically here, when importing AST_NODE_TYPES, there is no need for typescript to be imported.

I had to move the import of the package into the factory of my own custom parse function, and had to start importing AST_NODE_TYPES from @typescript-eslint/types instead, which solved the issue...until today where I imported again and without noticing AST_NODE_TYPES from @typescript-eslint/typescript-estree - thank you dear IDE.

I'm about to release a version that fix the issue one more time, but I'm sure that it will happen again, and I'm also sure that a lot of people are actually doing the same mistake without even noticing.

I'd like to request that either:

• @typescript-eslint/typescript-estree stops exporting AST_NODE_TYPES - to make sure that IDEs only import it from @typescript-eslint/types
• or that AST_NODE_TYPES is removed entirely and node types are replaced by strings (type: 'WhileStatement'), removing the dependency on an enum entirely while preserving type checking and autocompletion
• or that the typescript package is imported only when needed instead of as soon as @typescript-eslint/typescript-estree is imported