Cannot read properties of undefined (reading 'call') on massive code change/format

[njfamirm]

What version of Tailwind CSS are you using?

"@tailwindcss/vite": "^4.1.17",
"tailwindcss": "^4.1.17",

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

For example: Astro 5.16.0

---

What version of Node.js are you using?

For example: v24.11.0

What browser are you using?

For example: N/A

What operating system are you using?

For example: macOS

Reproduction URL

https://stackblitz.com/edit/github-ihhy81u7

Describe your issue

Hi

This error occurs intermittently and repeatedly for me. Our project is extremely large and massive (high complexity, high volume of files/dependencies), and this error primarily appears when a significant code change (e.g., mass formatting or refactoring) or a branch switch.

The error shows up in the browser and the terminal, effectively stopping the HMR process. To fix it, I have to manually stop the development server and restart it.

Unfortunately, I couldn't find a pattern where you could see the exact error again, but minimum configs provided

Logs:

Stack Trace

TypeError: Cannot read properties of undefined (reading 'call')

at EnvironmentPluginContainer.transform (/node_modules/astro/node_modules/vite/dist/node/chunks/dep-D4NMHUTW.js:42324:19)
at async loadAndTransform (file:///home/nexim-0/projects/order-next/node_modules/astro/node_modules/vite/dist/node/chunks/dep-D4NMHUTW.js:35739:27)
at async fetchModule (node_modules/astro/node_modules/vite/dist/node/chunks/dep-D4NMHUTW.js:46858:16)
at async handleInvoke (file:///home/nexim-0/projects/order-next/node_modules/astro/node_modules/vite/dist/node/chunks/dep-D4NMHUTW.js:39002:22)
at async EventEmitter.listenerForInvokeHandler (file://node_modules/astro/node_modules/vite/dist/node/chunks/dep-D4NMHUTW.js:39075:19)

// another log:

13:19:59 Configuration file updated. Restarting...

13:19:59 [watch] astro.config.mjs

13:19:59 [watch] astro.config.mjs

13:19:59 [assets] Copying fonts (21 files)...

13:19:59 [ERROR] transport was disconnected, cannot call "fetchModule"

Stack trace:

at /home/nexim-0/projects/order-next/packages/admin/home/nexim-0/projects/order-next/node_modules/astro/node_modules/vite/dist/node/module-runner.js:548:17

[...] See full stack trace in the browser, or rerun with --verbose.

13:20:00 [vite] Re-optimizing dependencies because vite config has changed

13:20:00 [content] Syncing content

13:20:00 [content] Synced content

13:20:00 [types] Generated 618ms

13:20:00 [vite] Re-optimizing dependencies because vite config has changed

13:20:01 [200] /service-worker.js 21ms

13:20:02 [ERROR] Cannot read properties of undefined (reading 'call')

Stack trace:

at /home/nexim-0/projects/order-next/packages/admin/src/shared/ui/Header.tsx

[...] See full stack trace in the browser, or rerun with --verbose.

13:20:04 [200] /service-worker.js 1ms

📦 @alwatr/package-tracer v5.5.23

📦 @nexim/tailwind-material-colors v1.0.4

📦 global-config v7.34.2

📦 global-config v7.34.2

13:20:13 [ERROR] Cannot read properties of undefined (reading 'call')

Stack trace:

at /home/nexim-0/projects/order-next/packages/admin/src/app/layouts/Pure.astro?astro&type=script&index=0&lang.ts

[...] See full stack trace in the browser, or rerun with --verbose.

13:20:20 [ERROR] Cannot read properties of undefined (reading 'call')

Stack trace:

at /home/nexim-0/projects/order-next/packages/admin/src/shared/ui/Header.tsx

[...] See full stack trace in the browser, or rerun with --verbose.

13:20:22 [200] /service-worker.js 1ms
// and in verbose mode when configuration changed

vite:load 0.31ms [fs] ../../node_modules/astro/dist/runtime/server/transition.js +1ms

vite:resolve 0.09ms ../../transitions/index.js -> /home/nexim-0/projects/order-next/node_modules/astro/dist/transitions/index.js +6ms

vite:import-analysis 0.32ms [2 imports rewritten] /home/nexim-0/projects/order-next/node_modules/astro/dist/runtime/server/transition.js +2ms

vite:transform 0.45ms ../../node_modules/astro/dist/runtime/server/transition.js +2ms

vite:load 0.37ms [fs] ../../node_modules/astro/dist/transitions/index.js +4ms

vite:resolve 0.06ms ../runtime/server/transition.js -> /home/nexim-0/projects/order-next/node_modules/astro/dist/runtime/server/transition.js +3ms

vite:import-analysis 0.21ms [1 imports rewritten] /home/nexim-0/projects/order-next/node_modules/astro/dist/transitions/index.js +3ms

vite:transform 0.34ms ../../node_modules/astro/dist/transitions/index.js +3ms

vite:load 0.28ms [fs] /src/shared/ui/Header.tsx +1ms

astro:vite Error when evaluating SSR module /home/nexim-0/projects/order-next/packages/admin/src/pages/inventory.astro: Cannot read properties of undefined (reading 'call')

astro:vite   Plugin: vite:react-babel

astro:vite   File: /home/nexim-0/projects/order-next/packages/admin/src/shared/ui/Header.tsx

astro:vite       at EnvironmentPluginContainer.transform (file:///home/nexim-0/projects/order-next/node_modules/astro/node_modules/vite/dist/node/chunks/dep-D4NMHUTW.js:42324:19)

astro:vite       at async loadAndTransform (file:///home/nexim-0/projects/order-next/node_modules/astro/node_modules/vite/dist/node/chunks/dep-D4NMHUTW.js:35739:27) +5s

13:21:36 [ERROR] Cannot read properties of undefined (reading 'call')

Stack trace:

at EnvironmentPluginContainer.transform (file:///home/nexim-0/projects/order-next/node_modules/astro/node_modules/vite/dist/node/chunks/dep-D4NMHUTW.js:42324:19)

vite:time 264.06ms /inventory/ +0ms




[njfamirm]

I'm check node_modules file and I think this happen based this object don't have transform

tailwindcss/packages/@tailwindcss-vite/src/index.ts

Lines 89 to 97 in 117433a

	{
	// Step 1: Scan source files for candidates
	name: '@tailwindcss/vite:scan',
	enforce: 'pre',
	configureServer(server) {
	servers.push(server)
	},

because in vite want to pass plugin.transform to getHookHandler

http://github.com/vitejs/vite/blob/d9ac20406cca3b32fc37c32a1c081881bf1ee897/packages/vite/src/node/server/pluginContainer.ts#L567-L570

[njfamirm]

also this type error exists (maybe not related to current issue)

// plugins: [tailwindcss()],

Type 'Plugin<any>[]' is not assignable to type 'PluginOption'.
  Type 'Plugin<any>[]' is not assignable to type 'PluginOption[]'.
    Type 'Plugin<any>' is not assignable to type 'PluginOption'.
      Type 'import("/home/nexim-0/projects/order-next/node_modules/vite/dist/node/index").Plugin<any>' is not assignable to type 'import("/home/nexim-0/projects/order-next/node_modules/@astrojs/react/node_modules/vite/dist/node/index").Plugin<any>'.
        Types of property 'hotUpdate' are incompatible.
          Type 'ObjectHook<(this: MinimalPluginContext & { environment: DevEnvironment; }, options: HotUpdateOptions) => void | EnvironmentModuleNode[] | Promise<...>> | undefined' is not assignable to type 'ObjectHook<(this: HotUpdatePluginContext, options: HotUpdateOptions) => void | EnvironmentModuleNode[] | Promise<void | EnvironmentModuleNode[]>> | undefined'.
            Type '(this: MinimalPluginContext & { environment: DevEnvironment; }, options: HotUpdateOptions) => void | EnvironmentModuleNode[] | Promise<...>' is not assignable to type 'ObjectHook<(this: HotUpdatePluginContext, options: HotUpdateOptions) => void | EnvironmentModuleNode[] | Promise<void | EnvironmentModuleNode[]>> | undefined'.
              Type '(this: MinimalPluginContext & { environment: DevEnvironment; }, options: HotUpdateOptions) => void | EnvironmentModuleNode[] | Promise<...>' is not assignable to type '(this: HotUpdatePluginContext, options: HotUpdateOptions) => void | EnvironmentModuleNode[] | Promise<void | EnvironmentModuleNode[]>'.
                The 'this' types of each signature are incompatible.
                  Type 'HotUpdatePluginContext' is not assignable to type 'MinimalPluginContext & { environment: DevEnvironment; }'.
                    Type 'HotUpdatePluginContext' is missing the following properties from type 'MinimalPluginContext': debug, error, info, meta, warnts(2322)

[ath1614]

@thecrypticace I would want to work on this issue!

[thecrypticace]

This feels like a potential Vite bug. Maybe related to some internal cache invalidation. 🤔

[thecrypticace]

also this type error exists (maybe not related to current issue)
…

I'm not seeing any type errors in a fresh install.

These kinds of type errors like this are almost always indicative of one of these:

• Multiple Vite versions
• The vite that's included by your project and by the plugin are coming from two different paths — even if they are the same version.

In your case it's probably the first one but not 100% sure.

[thecrypticace]

Yeah this definitely feels like a Vite bug.

This call to getSortedPlugins checks a cache and returns. If the list isn't cached it delegates to getSortedPluginsByHook which checks if a given hook exists for the plugins. In this case our scan plugin should not be in this list because transform isn't defined.

See:

• https://github.com/vitejs/vite/blob/a3cd262f37228967e455617e982b35fccc49ffe9/packages/vite/src/node/plugins/index.ts#L109-L111
• https://github.com/vitejs/vite/blob/a3cd262f37228967e455617e982b35fccc49ffe9/packages/vite/src/node/plugins/index.ts#L141-L143

My assumption is that the formatting causes Vite to rerun, probably multiple times, and there's a race condition inside Vite where the plugin cache is "stale" or somehow incorrect. Not quite sure — this will take some work to try to reproduce so i can file a bug report with them with enough detail.

[thecrypticace]

Yeah, I can't come up with a way to reproduce the problem. I'm guessing your large project exhibits some behavior that causes some internal stuff to wait too long and other stuff not to resulting in the race condition.

Something I'll note is that it looks like every time the error occurs in your logs it's processing Header.jsx while doing SSR for vite:react-babel. I wonder if there's something about that file + plugin that triggers the bug. 🤔

That particular plugin instance does have a transform but some of the others ones in that combo plugin don't.

[thecrypticace]

Okay, so I've done a bunch more reading of the code.

The important parts of the related code look to be mostly closure scoped so it doesn't feel like this is possible without something removing the transform hook from a plugin at runtime after an initial transform call somewhere. Our plugin doesn't do anything of the sort — nor can I think of a reason any plugin would need to.

I definitely don't think this an issue with us — and it might not even be an issue with Vite as far as I can tell. If you can reproduce this again later I'd ask that you edit the Vite source in your node_modules folder to log the relevant plugin to see which one it is and may see if you can see where it gets placed into the sorted plugins cache initially because that might be part of the problem.

if you can provide some more specific details based on my request above I'll definitely take another look because this is super strange and I'd love to track this down.

[njfamirm]

Thanks for your review

I spent a lot of time today trying to figure out what was going on with logging and stuff like that, but it didn't work

And I just saw something on a small project where the exact same thing happened! and I almost realized that there was a bug because nothing extra was configured in this project and everything was default.