@rollup/plugin-typescript

[sajermann]

Hi, I have a question!

If I configure "exclude" options in tsconfig.json doesn't generated types of files from folder excludes, but if I configure "exclude" options in rollup.config.js is generated only types of files from folder excludes, why is this happen?

Correctly

Wrong

Versions in my project:
"@rollup/plugin-typescript": "^8.3.4",
"rollup": "^2.77.2",

My Script for build:
"build": "npx rollup --config rollup.config.js",

[potatohoney-p]

The directory entries in the screenshots are not equivalent between the two exclude options. TypeScript's tsconfig.json exclusion can name a directory, whereas the plugin's exclude filters file paths using patterns. A plugin pattern of src/Pages does not match src/Pages/SomePage.tsx.

For the plugin configuration, use patterns that include the directory contents:

typescript({
  tsconfig: './tsconfig.json',
  exclude: [
    'src/Pages/**',
    'src/test/**',
    'src/App.tsx',
    'src/main.tsx',
    '**/*.spec.ts',
    '**/*.test.ts',
    '**/*.spec.tsx',
    '**/*.test.tsx'
  ],
  compilerOptions: {
    jsx: 'react-jsx',
    declaration: true,
    declarationDir: 'build'
  }
})

I reproduced the distinction with @rollup/plugin-typescript@8.3.4, rollup@2.77.2, TypeScript 4.7.4, tslib@2.4.0, and the historical picomatch@2.3.1 dependency, using a fresh output directory for each build. The fixture had a library entry/component plus unimported src/Pages/App.ts and src/test/setup.ts files:

Exclusion configuration	Page/test declarations emitted?	Library declarations emitted?
tsconfig.json: ['src/Pages', 'src/test']	No	Yes
Plugin: ['src/Pages', 'src/test']	Yes	Yes
Plugin: ['src/Pages/**', 'src/test/**']	No	Yes

All three builds completed without warnings. This isolates the pattern difference; it is not a run of your complete React project. The 8.3.4 plugin options document exclude as patterns and explain their filterRoot base. The example above assumes the project-root layout shown in your screenshot.

Also check an empty output directory when comparing results: a subsequent build that stops emitting a declaration does not necessarily remove a stale file from an earlier build. And exclusion is not an import boundary—if the library entry imports an application/test module, that dependency needs addressing separately rather than relying on exclude to make it disappear.