-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
gulp-typescript & gulp.src issue #186
Comments
use TS 1.7.5 until ng2 supports 1.8 |
Please read carefully. I have allowed unreachable code. It compiles and I don't see any compilation issues. And this actually doesn't matter. The problem - is that it compiles But because TS compiler sees I don't want to compile it in, because then I can't cache And one more point - if I just remove Do you see the point? |
Yeap, just add to ignore .ts files from node modules ng2 folders |
I have done it, but it ignores that parameter if you run with |
Can you add to ignore ts file from node modules in gulp files selector? (Blob) |
No, they are already ignored, because my selector includes only my files... |
Not cool, not cool at all On Thu, 18 Feb 2016, 20:19 Igor notifications@github.com wrote:
|
Dear Valor team,
Could you please fix the following issue:
If you use
gulp-typescript
specifying source files usinggulp.src
and you specify tooutFile
to build a bundle, typescript will include ng2-bootstrap into that bundle. If you includeng2-bootstrap.min.js
bundle on that page it won't work, if you don't - it won't work neither.The root cause:
Source
*.ts
files present in the same folder as*.js
files in npm module.And TypeScript just compiles it.
Exclude
option oftsconfig.json
won't work, as it is ignoring it.How to fix:
It's very simple please make dedicated folder
src
and include*.ts
files there. Other folders should contain only*.js
,*.js.map
,*.d.ts
and no original*.ts
files.Please take a look on Angular2 package for confirmation.
Workaround:
Currently we have to run gulp task to remove those files.
PS:
It will also fix issue #178
The text was updated successfully, but these errors were encountered: