
Security News
/Research
Popular node-ipc npm Package Infected with Credential Stealer
Socket detected malicious node-ipc versions with obfuscated stealer/backdoor behavior in a developing npm supply chain attack.
@doist/react-compiler-tracker
Advanced tools
A React Compiler violation tracker to help migrations and prevent regressions
The React Compiler automatically memoizes your components, eliminating the need for useCallback and useMemo. However, certain code patterns cause the compiler to bail out. When this happens, your components lose automatic optimization, potentially causing performance regressions.
Inspired by esplint and react-compiler-marker, this tool tracks compiler errors in a .react-compiler.rec.json file and integrates with Git hooks and CI to prevent new violations from being introduced.
This tool requires babel-plugin-react-compiler to be installed in your project:
npm install --save-dev babel-plugin-react-compiler
npm install --save-dev @doist/react-compiler-tracker
Create a .react-compiler-tracker.config.json file in your project root to customize the tool's behavior:
{
"recordsFile": ".react-compiler.rec.json",
"sourceGlob": "src/**/*.{js,jsx,ts,tsx}"
}
All fields are optional. Default values are shown above.
| Option | Description | Default |
|---|---|---|
recordsFile | Path to the records file | .react-compiler.rec.json |
sourceGlob | Glob pattern for source files | src/**/*.{js,jsx,ts,tsx} |
In a monorepo, run the tool from your package directory. The config file and all paths are relative to where you run the command. The defaults typically work out of the box:
my-monorepo/
├── packages/
│ └── frontend/
│ ├── .react-compiler-tracker.config.json # Optional config
│ ├── .react-compiler.rec.json # Records file
│ └── src/
│ └── ...
If your source files are in a different location (e.g., app/ instead of src/), customize the config:
{
"sourceGlob": "app/**/*.{ts,tsx}"
}
--overwriteRegenerates the entire records file by scanning all source files matching sourceGlob. Useful for initialization or picking up changes from skipped Git hooks.
npx @doist/react-compiler-tracker --overwrite
--stage-record-file <file1> <file2> ...Checks the provided files and updates the records. Exits with code 1 if errors increase (preventing the commit), otherwise updates the records file for the checked files. Reports when errors decrease, celebrating your progress. Deleted files are automatically removed from the records (no need to pass their paths).
npx @doist/react-compiler-tracker --stage-record-file src/components/Button.tsx src/hooks/useData.ts
If no files are provided, exits cleanly with a success message.
--check-files <file1> <file2> ...Checks specific files without updating records. Exits with code 1 if checked files show increased error counts (or new errors), or if any provided file does not exist. Reports when errors decrease, celebrating your progress. Primarily for CI to ensure PRs don't introduce new compiler errors.
npx @doist/react-compiler-tracker --check-files src/components/Button.tsx src/hooks/useData.ts
Checks all source files matching sourceGlob and reports the total error count. The records file is not updated in this mode.
npx @doist/react-compiler-tracker
--show-errorsShows error information from the compiler including file path, line number, and error reason. Can be combined with any command. Errors are displayed for all checked files regardless of whether they increased.
npx @doist/react-compiler-tracker --check-files --show-errors src/components/Button.tsx
Example output when errors have increased:
Errors:
- src/components/Button.tsx: Line 15: Cannot access refs during render (x2)
- src/components/Button.tsx: Line 28: Invalid hook usage
❌ React Compiler errors have increased in:
• src/components/Button.tsx: +3
Please fix the errors and run the command again.
When no new errors are introduced, you still see the existing errors:
Errors:
- src/components/Button.tsx: Line 15: Cannot access refs during render (x2)
âś… No new React Compiler errors in checked files
In package.json:
{
"lint-staged": {
"*.{js,jsx,ts,tsx}": "npx @doist/react-compiler-tracker --stage-record-file"
}
}
With lint-staged, the matched files are automatically passed as arguments to the command.
- name: Check React Compiler violations
run: |
# Get changed files in the PR
FILES=$(git diff --name-only origin/main...HEAD -- '*.tsx' '*.ts' '*.jsx' '*.js' | tr '\n' ' ')
if [ -n "$FILES" ]; then
npx @doist/react-compiler-tracker --check-files $FILES
fi
#!/bin/sh
# Get staged files and pass them to the tracker
# (deleted files are auto-detected from records, no need to pass them)
FILES=$(git diff --diff-filter=ACMR --cached --name-only -- '*.tsx' '*.ts' '*.jsx' '*.js' | tr '\n' ' ')
if [ -n "$FILES" ]; then
npx @doist/react-compiler-tracker --stage-record-file $FILES
fi
This project uses release-please to automate releases. Commits merged to main with fix: trigger patch releases, feat: triggers minor releases, and feat!: or fix!: triggers major releases.
When commits land on main, release-please creates a release PR. Merging it publishes to npm and GitHub Packages.
Released under the MIT License.
FAQs
A React Compiler violation tracker to help migrations and prevent regressions
The npm package @doist/react-compiler-tracker receives a total of 718 weekly downloads. As such, @doist/react-compiler-tracker popularity was classified as not popular.
We found that @doist/react-compiler-tracker demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 9 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
/Research
Socket detected malicious node-ipc versions with obfuscated stealer/backdoor behavior in a developing npm supply chain attack.

Security News
TeamPCP and BreachForums are promoting a Shai-Hulud supply chain attack contest with a $1,000 prize for the biggest package compromise.

Security News
Packagist urges PHP projects to update Composer after a GitHub token format change exposed some GitHub Actions tokens in CI logs.