Release loader callbacks after compilation

[tamird]

Summary

Cached compilers retain the module and stylesheet loader callbacks after compilation. Callbacks supplied by build tools can capture completed build state, keeping it alive during later builds.

Capture the from and polyfills values used by subsequent builds and isolate config and plugin loading from the compatibility theme resolver's scope. This allows the loader callbacks and their captured state to be collected after compilation.

Test plan

The regression keeps the compiler alive across garbage collection, verifies that both loader callbacks can be collected, and confirms that a subsequent utility build still works.

• corepack pnpm test:integrations postcss/compiler-lifetime.test.ts (Node.js 24.19.0)
• corepack pnpm run test (Node.js 24.19.0)
• corepack pnpm build (Node.js 22.23.3)

The complete integration suite remains unverified locally because several framework fixtures require filesystem and network capabilities unavailable in the sandbox. Lint stopped on generated files and embedded templates; the scoped type check reports the same diagnostics on the unchanged base.

[greptile-apps]

Confidence Score: 5/5

[Medium risk] Refactors compiler memory management to release loader callbacks.

The PR appears safe to merge.

_{Reviews (1) · Last reviewed commit: "Release loader callbacks after compilati..."}

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Advanced

Run ID: 7bdc73aa-cb18-46f7-8c8d-588414bf4f9c

📥 Commits

Reviewing files that changed from the base of the PR and between fa81d69 and e8e1178.

📒 Files selected for processing (3)

• integrations/postcss/compiler-lifetime.test.ts
• packages/tailwindcss/src/compat/apply-compat-hooks.ts
• packages/tailwindcss/src/index.ts

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

Walkthrough

The compiler captures source-location and polyfill options in local values. Compatibility config and plugin loading move into a helper. A PostCSS integration test checks that loader callbacks can be collected while the compiler can still build CSS containing .flex.

Priority: ➖ Normal

Merge Risk: ⚪ Minimal · up to e8e11

The changes preserve compilation behavior while allowing loader callbacks to be released. The regression retains a usable compiler through collection checks. No actionable merge-blocking risk remains beyond normal validation.

Security Architecture Review

Security architecture risk: 🔵 Low · up to e8e11

The inspected change reduces retained build state without broadening module-loading authority. No introduced security concern was identified, but failure, concurrency, and downstream integration behavior have not been fully verified.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

• inferred — The evidenced exposure remains the compiling host's loader policy and retained compiler state. Control of stylesheet directives can influence the module IDs sent to that loader, but the inspected change does not broaden the available loader authority. Tenant isolation, credentials, service exposure, and deployment-specific permissions are not established by the supplied context.

Trust Boundaries and Controls

• observed — Base-to-head comparison preserves top-level directive restrictions, plugin option parsing, context-derived base/reference/source metadata, and the config/plugin resource hints passed to the loader. The changed aliases and helper do not introduce a new route around those checks.

Resilience and Maintainability Implications

• inferred — A rejected compatibility load still prevents successful compiler publication. The unchanged Promise.all structure does not cancel other in-flight loader work or roll back loader side effects, so rejection is not transactional isolation. That limitation predates this extraction; no new failure-containment weakness was identified in the inspected transition.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: releasing module and stylesheet loader callbacks after compilation.
Description check	✅ Passed	The description accurately explains callback retention, garbage collection, cached compiler behavior, implementation changes, and test coverage.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}