Skip to content

outDir changes when importing angular2-moment #37

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

Closed
ghost opened this issue May 14, 2016 · 3 comments
Closed

outDir changes when importing angular2-moment #37

ghost opened this issue May 14, 2016 · 3 comments

Comments

@ghost
Copy link

ghost commented May 14, 2016

As soon as I use an import-statement to include a file as a pipe, my build scripts stop working properly.
If my code is in /src, and I want everything inside /src to be compiled to /public it works as expected without an import.
So for example, /src/test.ts becomes /public/test.{map.}js.
As soon as I import this module, it adds another directory (the src directory)
So /src/test.ts becomes /public/src/test.{map.}js suddenly...

Other projects seem to have similar problems. See this issue from ng2-bootstrap: valor-software/ngx-bootstrap#128

Here is a Stackoverflow question, describing the very same problem I have (also, for ng2-bootstrap)
http://stackoverflow.com/questions/35648347/importing-ng2-bootstrap-changes-my-tsc-output-directory-structure

I hope this gets fixed soon, as I cant use this module if it messes up my whole directory structure...

Edit: I can confirm that this issue gets fixed if .ts (not .d.ts) files are moved into a separate directory

@urish
Copy link
Owner

urish commented May 22, 2016

Hi, just released 0.8.0, where the .ts files were moved to a separate directory, as you suggested.

Can you please verify that this indeed solved your issue?

@urish urish closed this as completed May 22, 2016
@ghost
Copy link
Author

ghost commented May 22, 2016

Thank you very much for the fix :)
I will try it tomorrow and let you know then

@ghost
Copy link
Author

ghost commented May 23, 2016

Issue is resolved! Thank you very much for your quick fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant