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
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...
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
The text was updated successfully, but these errors were encountered: