-
Notifications
You must be signed in to change notification settings - Fork 181
fails with typescript 2.1.4 #293
Comments
Quick fix/hack: Edit the following file: Line ~142: _.defaults(compilerConfig.options, {
sourceMap: true,
verbose: false,
skipDefaultLibCheck: true,
suppressOutputPathCheck: true
});
if (loaderConfig.transpileOnly) {
compilerConfig.options.isolatedModules = true;
}
_.defaults(compilerConfig.options, {
sourceRoot: compilerConfig.options.sourceMap ? process.cwd() : undefined
});
_.defaults(loaderConfig, {
sourceMap: true,
verbose: false,
});
delete compilerConfig.options.outDir;
delete compilerConfig.options.inlineSourceMap;
delete compilerConfig.options.outFile;
delete compilerConfig.options.out;
delete compilerConfig.options.noEmit; |
Still not working with typescript 2.1.1 |
Which version of the loader this is related to? |
3.10.8 |
This happens with 2.2.4. 3.0.0-beta.9 works fine with TypeScript 2.1.4. |
I have the same problem with typescript 2.0.3 and awesome-typescript-loader 2.2.4 |
i have the same problem with awesome-typescript-loader 3.10.8 and typescript 2.1.1 and 2.0.10 |
got it working here, had to lock down typescript version {
"awesome-typescript-loader": "^2.2.4",
"typescript": "2.0.10"
} |
It fine works with locked 2.0.3 typescript version |
working with typescript 2.1.1 |
Using typescript 2.1.4 and awesome-typescript-loader version 2.2.4. |
Same problem, pinned to Typescript 2.1.1 and it works. |
* chore(package): pins TypeScript version to 2.1.1 - Relavent issue: s-panferov/awesome-typescript-loader#293
Version 2.1.4 renames typingOptions from compilerConfig to typeAcquisition. See PR microsoft/TypeScript#12373. So typingOptions is no longer available. So instance.js breaks on compilerConfig.typingOptions.exclude. |
Works for me on beta.
|
If it is only renaming some options ( |
Since beta has issues with remapping code coverage, this would be ideal. |
Fixed to me : "awesome-typescript-loader": "2.2.4" |
Its fixed with "typescript": "^2.1.4" and "awesome-typescript-loader": "^3.0.0-beta.9" |
What's the status? Object spread/rest is not working in 2.1.1. It would be nice to be able to upgrade and get rid of |
@faddee I'm running 3.0.0-beta.17 and have no problems. |
We are also stuck to the 2.2 version, since 3.0's |
still a problem 😢 |
Fixes ``` TypeError: Cannot read property 'exclude' of undefined at applyDefaults ``` cf. s-panferov/awesome-typescript-loader#293
Using version I faced this issue using awesome-typescript-loader 2.2.4 with typescript 2.1.4 (working though with typescript 2.0.10). |
In tsconfig.json, I configured the following: Then I am able use ATL 3.2.1 and Typescript 2.2.1 |
had error using awesome-typescript-loader 2.2.4 and typescript 2.0.10 fixed with @snerks quick fix. |
Nothing worked. tried everything in this thread :(
ERROR in ./src/vendor.ts |
We gave up waiting months and switched to |
@DenisVuyka can you guide me please. |
@dksharp You can refer to the official webpack guide for TypeScript that is now featuring |
|
It's working. |
@rafaelsobreirabraga The issue still there. |
Updating from typescript 2.1.1 to 2.1.4 yields the following error:
This is my tsconfig.json:
The text was updated successfully, but these errors were encountered: