-
-
Notifications
You must be signed in to change notification settings - Fork 431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Definition files generation with semi absolute path inside of build directory #186
Comments
Any progress on this? It makes emitting typings with webpack pointless since the paths are all wrong. Thanks! |
It's relating to a different issue, but I think there's a decent chance the pull request (#214) I submitted might fix this - although at the minute the file paths are based on the current working directory, rather than being relative to the entry point, which I don't think is quite right. It's a start, though. |
@jbrantly Can you comment about this issue? Thanks! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
1 similar comment
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Closing as stale. Please reopen if you'd like to work on this further. |
Since version 0.8.2, all
d.ts
files are now generated with full absolute path inside build directory (the one set on webpack configuration).For example, considering I have
outDir
set tots-build
ontsconfig.json
, I have:Instead of
This issue is initially reported by @bartzy and myself on #175.
The text was updated successfully, but these errors were encountered: