Still getting issue "TS18003: No inputs were found in config file 'tsconfig.json'"

Hi,

I am currently building a more-or-less zero config bundler for our company’s internal usage. For this I want to add TypeScript support using ts-loader without needing any of our dozens of projects to add a tsconfig.json.

Expected Behaviour

It should just work, as there is an option in the plugin to set a custom path for the tsconfig.json.

Actual Behaviour

It doesn’t work and errors out with

TS18003: No inputs were found in config file ‘tsconfig.json’. Specified ‘include’ paths were ‘[“**/*”]’ and ‘exclude’ paths were ‘[]’.

Steps to Reproduce the Problem

I installed your vanilla example and did the following adjustments:

• move tsconfig.json to example/tsconfig.json

• change the webpack config to point to the new config file:

  module: {
      rules: [
          {
              test: /\.tsx?$/,
              loader: 'ts-loader',
              options: {
                  configFile: __dirname + "/test/tsconfig.json" // <- this is new
              }
          }
      ]
  },
  

Location of a Minimal Repository that Demonstrates the Issue.

[apfelbox]

@johnnyreilly it actually worked using context, thank you! I was already desparate, as nothing seemed to work. Thank you very much for the fast answer! I will send a PR though, to suggest an improvement in the docs.

@theironcook I think you have an other issue, I think you are using invalid babel loader syntax. There are two variations (there are actually more, but two that matter):

1. with a single loader

{
    test: /\.ts?$/, 
    loader: 'ts-loader', 
    exclude: /node_modules/, 
    options: { 
        context: __dirname, 
        configFile: 'tsconfig.client.json' 
    },
}

or 2) with a list of loaders:

{
    test: /\.ts?$/, 
    exclude: /node_modules/, 
    use: [
        {
            loader: 'ts-loader', 
            options: { 
                context: __dirname, 
                configFile: 'tsconfig.client.json' 
            },
        }
    ]
}

You have a mix of both, but need to use loader as key. That is what the error message is trying to tell you, they literally mean the object key loader in

options / query provided without loader

[apfelbox]

I will close this issue, as we now have an open PR to keep the discussion going in #733