Do you have it installed globally, or locally in the project? Why do you try to import it using absolute path instead of using module ID as it has to be done with packages installed in node_modules?
Its installed locally and has "typings" property in its package.json file.
These codes are generated by build tools dynamically maybe for compatibility reasons, so i can't modify them as they are regenerated whenever i change my code.
I have tried `tsc --traceResolution` and there is no problem with result.
Import via module name works as expected.
Do you have it installed globally, or locally in the project? Why do you try to import it using absolute path instead of using module ID as it has to be done with packages installed in node_modules?
Its installed locally and has "typings" property in its package.json file.
These codes are generated by build tools dynamically maybe for compatibility reasons, so i can't modify them as they are regenerated whenever i change my code.
I have tried `tsc --traceResolution` and there is no problem with result.
Using 'dva` instead of full absolute path is the only way to go, such paths in import/require are not supported