-
Notifications
You must be signed in to change notification settings - Fork 19
Do not work with "--allowJs" option #39
Comments
@qtuan I have added a test to check that the flag is passed on to TypeScript. The issue must be something else. |
@jrieken Thanks for checking! Could you speculate what is wrong? I couldn't figure it out. Here is my test data:
Build script is same as in my original post.
Version of installed packages: |
@qtuan Can you try to define the |
@jrieken Actually I tried Another point I forget to mention, that I need to
My environment: |
The builder only allows for Line 471 in b040fa1
This should be changed to also include getScriptFileNames(): string[] {
const result: string[] = [];
const libLocation = this.getDefaultLibLocation();
const filter = this._settings.allowJs ? /\.?(ts|tsx|js)/i : /\.?(ts|tsx)/i;
for (let fileName in this._snapshots) {
if (filter.test(path.extname(fileName))
&& normalize(path.dirname(fileName)) !== libLocation) {
// only ts-files and not lib.d.ts-like files
result.push(fileName);
}
}
return result;
} |
@jrieken, this is a great enhancement to the build I believe I'm running into this same issue with it not generating output objects for .js files in the input stream, despite I see @zenorbi has a PR which sounds like it may fix it. What's the likelihood of getting this applied to the published version sometime soon? Instrumentation from gulp.debug around the gulp-tsb step:
|
Typescript 1.8 support
--allowJs
, but gulp-tsb seems to ignore it.Correct output files are still generated for respective source
*.ts
, but none is generated for the*.js
files.It works correctly when running
tsc
on the command line.The text was updated successfully, but these errors were encountered: