Give better error messages for bare imports with badly configured projects

[DanielRosenwasser]

When targeting es2015 or later, moduleResolution isn't set to node by default.

Perhaps when

• moduleResolution is calculated to be classic and
• paths aren't specified

we should hint to the user

Did you mean to set the 'moduleResolution' option to 'node', or to add aliases to the 'paths' option?

[danielkcz]

I want to add here, that the Playground does not even allow to set a moduleResolution.

I tried reproducing some errors and was confused about why am I getting different outcomes in the playground compared to my actual code.

Only after fiddling with it CodeSandbox I eventually found out that moduleResolution: node did the trick.

I was not able to find if Playground issues should be reported somewhere else. Should I open a separate issue here?

Why is the classic resolution still being kept as default for a new module types?

[DanielRosenwasser]

Yes, https://github.com/Microsoft/TypeScript-Website, though I would say the website should probably just always display moduleResolution: node since anything else is useless.

Why is the classic resolution still being kept as default for a new module types?

Yeah, there's #11434 but I don't think we ever got around to the work.

[orta]

The playground side of this is done (it always defaults to moduleResolution: node. )

Which leaves the warning on imports to do 👍

[mshivaku99]

Can me and @nityatammana work on this?