CLI watch does not rebuild when a tracked dependency is deleted

[fallintoplace]

What version of Tailwind CSS are you using?

v4.3.0

What build tool (or framework if it abstracts the build tool) are you using?

@tailwindcss/cli v4.3.0

What version of Node.js are you using?

v24.15.0

What browser are you using?

N/A

What operating system are you using?

macOS

Reproduction URL

N/A (fresh-project reproduction steps below)

Describe your issue

If a file in the CLI watcher's tracked full-rebuild dependency set is deleted, the watcher does not trigger a full rebuild.

I can reproduce this with a config dependency:

1. Create these files in a fresh project:

package.json

{
  "private": true,
  "dependencies": {
    "tailwindcss": "4.3.0",
    "@tailwindcss/cli": "4.3.0"
  }
}

tailwind.config.js

const myColor = require('./my-color')
module.exports = {
  theme: {
    extend: {
      colors: {
        primary: myColor,
      },
    },
  },
}

my-color.js

module.exports = 'blue'

src/index.css

@import 'tailwindcss';
@config '../tailwind.config.js';

index.html

<div class="text-primary"></div>

2. Install dependencies.
3. Run:

pnpm tailwindcss --input src/index.css --output dist/out.css --watch

4. Delete my-color.js.

Expected behavior:

• the watcher should trigger a full rebuild because my-color.js is a tracked rebuild dependency
• the rebuild should surface the missing dependency error instead of silently keeping stale state

Actual behavior:

• no rebuild is triggered on delete
• the previous CSS output stays in place until some other tracked full-rebuild file changes

This seems to happen because delete events are dropped before the watcher checks whether the deleted path is in the full rebuild dependency set.

[RobinMalfait]

Hey! This should be fixed by #20137, and will be available in the next release.

You can already try it by using the insiders build npm install tailwindcss@insiders.