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
In my build scenario, all compilerOptions are passed within the Webpack configuration. There are no tsconfig.json files anywhere in the source tree. Webpack configuration files are generatedon-the-fly based on information in a project repository (a database).
The error seems to arise from an empty configuration that is created (in config.js line 46). For some reason, this results in an error with compiler.parseJsonConfigFileContent (config.js line 99). I didn't investigate further into the typescript compiler to see why this is the case. I also don't see changes with respect to 1.2.2 which might cause this.
A small change seems to fix this:
//config.ts line 46
configFile = {
config: {
compilerOptions: {},
// files: [], // As it exists in the repo as of 1.3.3
files: [ loader.resourcePath ] // Line changed to add current resource path
},
};
A bug or by-design?
The text was updated successfully, but these errors were encountered:
In my build scenario, all compilerOptions are passed within the Webpack configuration. There are no tsconfig.json files anywhere in the source tree. Webpack configuration files are generatedon-the-fly based on information in a project repository (a database).
While this used to work with [email protected] and [email protected], it no longer does with [email protected]. Now ts-loader terminates with error:
error TS18002: The 'files' list in config file 'tsconfig.json' is empty
I tried the following combinations:
[email protected] and [email protected] // <- Fails!
[email protected] and [email protected] // <- Fails!
[email protected] and [email protected] // <- Works!!
The error seems to arise from an empty configuration that is created (in config.js line 46). For some reason, this results in an error with compiler.parseJsonConfigFileContent (config.js line 99). I didn't investigate further into the typescript compiler to see why this is the case. I also don't see changes with respect to 1.2.2 which might cause this.
A small change seems to fix this:
//config.ts line 46
configFile = {
config: {
compilerOptions: {},
// files: [], // As it exists in the repo as of 1.3.3
files: [ loader.resourcePath ] // Line changed to add current resource path
},
};
A bug or by-design?
The text was updated successfully, but these errors were encountered: