Skip to content
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

Closed
mrblackus opened this issue Apr 14, 2016 · 6 comments
Labels

Comments

@mrblackus
Copy link

mrblackus commented Apr 14, 2016

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 to ts-build on tsconfig.json, I have:

.
├── Users
│   └── mrblackus
│       └── Projects
│           └── js
│               └── fooProject
│                   └── build
│                       └── ts-build
│                           └── foo.d.ts
├── foo.js
└── foo.js.map

Instead of

.
├── foo.js
├── foo.js.map
└── ts-build
    └── foo.d.ts

This issue is initially reported by @bartzy and myself on #175.

@bartzy
Copy link

bartzy commented May 26, 2016

Any progress on this?

It makes emitting typings with webpack pointless since the paths are all wrong.

Thanks!

@17cupsofcoffee
Copy link
Contributor

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.

@bartzy
Copy link

bartzy commented Aug 2, 2016

@jbrantly Can you comment about this issue? Thanks!

@stale
Copy link

stale bot commented Jan 19, 2019

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
@stale
Copy link

stale bot commented Mar 20, 2019

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.

@stale stale bot added the wontfix label Mar 20, 2019
@stale
Copy link

stale bot commented Mar 27, 2019

Closing as stale. Please reopen if you'd like to work on this further.

@stale stale bot closed this as completed Mar 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants