Update the reason for not fixing types

[h-joo]

These type originate from node_modules and as the compiler refuses to create proper type node for them as it would be adding an import to node_modules. We also don't do anything about it.

[dragomirtitian]

@h-joo that is very interesting. Any idea why it fails? Is it hardcoded to do that for node_modules?

[h-joo]

@h-joo that is very interesting. Any idea why it fails? Is it hardcoded to do that for node_modules?

Yes, if you're curious, you can look for a comment containing node_modules in checker.ts.
It says :

// If ultimately we can only name the symbol with a reference that dives into a `node_modules` folder, we should error
// since declaration files with these kinds of references are liable to fail when published :(

[dragomirtitian]

Intresting. For example in [this](https://github.com/bloomberg/TypeScript/blob/92b3dcb1a2eba2750624b585bc9f905305883ba0/tests/cases/conformance/node/nodeModulesExportsBlocksSpecifierResolution.ts) test, ashould beThing` in my opinion. And there is already an import for that. So, this still seems suspect to me, but this was definitely an existing behavior.

Improving the type printing algorithm is not in our scope so it's fine to just put that as te reason for the failure.