Vite build starts fails when upgrading @tailwindcss/vite package to >4.0.7

[febkosq8]

My dockerfile build have started failing ever since 4.0.8 to @tailwindcss/vite package and I am not sure what is causing it.
Last I checked GitHub issues, didn't find anything similar.

Docker logs below :

[internal] load build definition from Dockerfile
transferring 1.5 kB 0.0s
[internal] load metadata for docker.io/library/node:22.12.0
[internal] load metadata for docker.io/library/nginx:1.27.4
[internal] load .dockerignore
[build 1/10] FROM docker.io/library/node:22.12.0@sha256:0e910f435308c36ea60b4cfd7b80208044d77a074d16b768a81901ce938a62dc
resolve docker.io/library/node:22.12.0@sha256:0e910f435308c36ea60b4cfd7b80208044d77a074d16b768a81901ce938a62dc 0.0s
[stage-1 1/6] FROM docker.io/library/nginx:1.27.4@sha256:9d6b58feebd2dbd3c56ab5853333d627cc6e281011cfd6050fa4bcf2072c9496
resolve docker.io/library/nginx:1.27.4@sha256:9d6b58feebd2dbd3c56ab5853333d627cc6e281011cfd6050fa4bcf2072c9496 0.0s
[internal] load build context
transferring 1.1 MB 0.1s
[build 2/10] COPY package*.json ./
<BUILD STEPS 3-5 HIDDEN FOR SENSITIVE INFO>
[build 6/10] RUN apt-get update
Get:1 http://deb.debian.org/debian bookworm InRelease [151 kB]
Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
Get:3 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Get:4 http://deb.debian.org/debian bookworm/main amd64 Packages [8792 kB]
Get:5 http://deb.debian.org/debian bookworm-updates/main amd64 Packages [13.5 kB]
Get:6 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages [246 kB]
Fetched 9306 kB in 3s (2917 kB/s)
Reading package lists...
[build 7/10] RUN npm ci
added 548 packages, and audited 549 packages in 42s
124 packages are looking for funding
run `npm fund` for details
4 low severity vulnerabilities
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
npm notice
npm notice New major version of npm available! 10.9.0 -> 11.2.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.2.0
npm notice To update run: npm install -g [email protected]
npm notice
[build 8/10] COPY . .
[build 9/10] RUN npm run build
> [email protected] build
> vite build
vite v6.2.1 building for production...
transforming...
thread '<unnamed>' panicked at crates/oxide/src/scanner/allowed_paths.rs:115:10:
called `Option::unwrap()` on a `None` value
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
Aborted (core dumped)

The build works fine when the @tailwindcss/vite package is 4.0.7 or lower
The build also works fine in my windows system, only in docker, the vite build step is failing

Current installed deps

[email protected]
├── @febkosq8/[email protected]
├── @floating-ui/[email protected]
├── @fortawesome/[email protected]
├── @fortawesome/[email protected]
├── @fortawesome/[email protected]
├── @headlessui/[email protected]
├── @radix-ui/[email protected]
├── @rinzai/[email protected]
├── @tailwindcss/[email protected]
├── @tailwindcss/[email protected]
├── @tanstack/[email protected]
├── @tanstack/[email protected]
├── @tanstack/[email protected]
├── @tanstack/[email protected]
├── @tanstack/[email protected]
├── @tanstack/[email protected]
├── @testing-library/[email protected]
├── @testing-library/[email protected]
├── @testing-library/[email protected]
├── @tiptap/[email protected]
├── @tiptap/[email protected]
├── @tiptap/[email protected]
├── @tiptap/[email protected]
├── @tiptap/[email protected]
├── @tiptap/[email protected]
├── @tiptap/[email protected]
├── @tiptap/[email protected]
├── @tiptap/[email protected]
├── @tiptap/[email protected]
├── @tiptap/[email protected]
├── @tiptap/[email protected]
├── @tiptap/[email protected]
├── @tiptap/[email protected]
├── @tiptap/[email protected]
├── @tiptap/[email protected]
├── @tiptap/[email protected]
├── @tiptap/[email protected]
├── @tiptap/[email protected]
├── @tiptap/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @vitejs/[email protected]
├── @vitest/[email protected]
├── @vitest/[email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

[febkosq8]

I enabled debug logs in vite and set RUST_BACKTRACE in env to full.

1.319   webSocketToken: 'uJRXy9nHQWOE',
1.319   getSortedPlugins: [Function: getSortedPlugins],
1.319   getSortedPluginHooks: [Function: getSortedPluginHooks],
1.319   createResolver: [Function: createResolver],
1.319   fsDenyGlob: [Function: arrayMatcher],
1.319   safeModulePaths: Set(0) {},
1.319   additionalAllowedHosts: []
1.319 }
1.321 vite v6.2.1 building for production...
1.550 transforming...
1.638 2025-03-07T14:31:39.990Z vite:resolve 0.12ms tailwindcss -> null
1.730 2025-03-07T14:31:40.081Z vite:resolve 0.06ms @tailwindcss/forms -> null
1.730 2025-03-07T14:31:40.081Z vite:resolve 0.24ms tailwind-scrollbar -> null
2.361 
2.361 thread '<unnamed>' panicked at crates/oxide/src/scanner/allowed_paths.rs:115:10:
2.361 called `Option::unwrap()` on a `None` value
2.361 stack backtrace:
2.361    0:     0x7f13a26ff4fc - <unknown>
2.361    1:     0x7f13a26207e3 - <unknown>
2.361    2:     0x7f13a26fec22 - <unknown>
2.362    3:     0x7f13a26ff1f3 - <unknown>
2.362    4:     0x7f13a26fea45 - <unknown>
2.362    5:     0x7f13a272f955 - <unknown>
2.362    6:     0x7f13a272f8e9 - <unknown>
2.362    7:     0x7f13a272fecc - <unknown>
2.362    8:     0x7f13a25cc7cf - <unknown>
2.362    9:     0x7f13a25cc81b - <unknown>
2.364   10:     0x7f13a25ccb38 - <unknown>
2.364   11:     0x7f13a277dd56 - <unknown>
2.364   12:     0x7f13a27593f9 - <unknown>
2.364   13:     0x7f13a273e1cc - <unknown>
2.364   14:     0x7f13a2736335 - <unknown>
2.381   15:           0xf25025 - _ZN6v8impl12_GLOBAL__N_123FunctionCallbackWrapper6InvokeERKN2v820FunctionCallbackInfoINS2_5ValueEEE
2.381   16:     0x7f13c3e0f5e2 - <unknown>
2.381 fatal runtime error: failed to initiate panic, error 5
11.07 Aborted (core dumped)
------
Dockerfile:29
--------------------
  27 |     RUN npm ci
  28 |     COPY . .
  29 | >>> RUN npm run build

If anyone has any clue, why this is happening. Please let me know.

[SIRHAMY]

I'm getting the same issue.

• Running locally on Linux with the npx command - outputs correctly
• Running in Docker Linux with the same npx command - fails with that error

Error message:

RUN npx @tailwindcss/cli -i ./Styles/tailwind.css -o ./out/tailwind.css:
0.873 thread '<unnamed>' panicked at crates/oxide/src/scanner/allowed_paths.rs:115:10:
0.873 called `Option::unwrap()` on a `None` value
0.873 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
0.873 fatal runtime error: failed to initiate panic, error 5
4.926 Aborted (core dumped)

I tried several different Node Docker base images to see if maybe it was a distro:

• 20-slim
• 22-slim
• 23-bullseye
• 23-bookworm
• 23-alpine

Each of these failed in the same way so I think it does have something to do with CLI running inside Docker for some reason.

[jbasko]

I had the same issue and found solution in this: dfinity/oisy-wallet#4831

With TailwindCSS 4 you have to do @import "tailwindcss" source("../"); with source( part according to your project structure.

[SIRHAMY]

Worked for me - thanks!

(Previously I was trying to use @source as laid out in the Tailwind v4 blog post but that didn't seem to work but including it on the same line with source() seems to work in Docker)

[febkosq8]

Can confirm that changing
@import "tailwindcss"; to @import "tailwindcss" source("../src"); in my index.css fixed the crash for me and runs the build as normal.

The exact details are here