rstackjs / rstackjs/ts-checker-rspack-plugin

Since 1.3.0 the exclude files config option doesn't work properly

Open
#73 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
28
Forks
8
Avg merge
1h 59m
Merged PRs (30d)
6

Description

Current behavior

Given this config as an example:

new TsCheckerRspackPlugin({
  issue: {
    include: [{ file: 'src/my/dir/**/*.{ts,tsx}' }],
    exclude: [{ file: 'src/my/dir/temp/*.ts' }],
  },
});

where you exclude some files within an included dir.

In 1.3.0 if I don't have any exclude I get some errors in multiple files.
Then if I add one of the problem files to the exclude list it then passes, even though there are still errors in the other files.

Expected behavior

Regardless of what is in the exclude files list, errors in included files should be caught.
This worked properly in 1.2.6 and earlier versions, and is one of the advantages of this project over using tsc directly.

Steps to reproduce the issue

  • Have a directory with at least 2 files.
  • Have errors in both files.
  • Have that directory in the include config.
  • Have one of the files in the exclude config.
  • The build will pass when it should fail.

Issue reproduction repository

Environment

  • ts-checker-rspack-plugin: 1.3.0
  • typescript: 4.9.5
  • @rspack/core: 1.4.10
  • os: macOS 26.2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported configuration with a directory containing two TypeScript files, errors in both, one included directory, and one excluded file. Compare behavior between versions 1.3.0 and 1.2.6, then trace the include/exclude handling; done means errors in all included files are still reported even when one file is excluded.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.