You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Related to issue #24599 , where @mhegazy specifically asks to create a separate ticket with more information when using latest typescript@next (^3.0.0-dev.20180630")
Imports get's node_modules added, which breaks Library conventions.
It's easy to replicate.
import ex. a library like @material-ui, which you have as a dependency.
In the output d.ts file one would
expect: import("@material-ui....
but result is: import("node_modules/@material-ui...
Hope information is sufficient.
The text was updated successfully, but these errors were encountered:
felixknox
changed the title
typescript@next (and 2.9.x) outputs node_modules relate path to imports
typescript@next (and 2.9.x) outputs node_modules relative path to imports
Jun 30, 2018
Related to issue #24599 , where @mhegazy specifically asks to create a separate ticket with more information when using latest typescript@next (^3.0.0-dev.20180630")
Imports get's
node_modules
added, which breaks Library conventions.It's easy to replicate.
import ex. a library like @material-ui, which you have as a dependency.
Using a tsconfig file like
Will take a .tsx file like:
And output a d.ts file like:
In the output d.ts file one would
expect:
import("@material-ui...
.but result is:
import("node_modules/@material-ui...
Hope information is sufficient.
The text was updated successfully, but these errors were encountered: