Go to Definition for Non JS/TS File Imports

From https://github.com/Microsoft/vscode/issues/24276

Issue Users of tools such as webpack often load non js/ts assets, such as css or images, using require or import:

require('./main.css');
import './image.png'
...

Operations such as go to definition currently do not work on these paths

Proposal go to definition on these resource paths should try to open the corresponding resource in the editor.

[jpike88]

Additionally TypeScript should be checking the path of EVERY import that occurs (module or otherwise) and raise an appropriate error. A hacky workaround silences an error that an html file isn’t a module, but an incorrect relative path doesn’t re-flag an error. So I’m stuck guessing that my import paths are hopefully correct.

https://github.com/Microsoft/vscode/issues/48025#issuecomment-382623046

I don’t get the argument regarding strict ES6 spec compliance. This is something webpack, fusebox and pretty much every bundler out there allows and encourages. I’d imagine this has plenty of devs out there using it. Widespread real-world use cases matter, so the meaning of what is and isn’t ‘compliant’ needs to be re-evaluated in this case.

Besides if this needs to be supported by the core, and maybe just have an appropriate .tsconfig flag turned off by default, why not just do it?

[chkpnt]

Yes, go to definition works. But how can I get rid of the warning “Cannot find module ‘…/img/bla.png’ or its corresponding type declarations.ts(2307)” while preserving this feature?

If I declare module '*.png' in global.d.ts the warning disappears, but then I’m again unable to use go-to-definition.