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

febkosq8 · 2025-03-07T09:06:18Z

febkosq8
Mar 7, 2025

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 npm@11.2.0
npm notice
[build 8/10] COPY . .
[build 9/10] RUN npm run build
> dlg.viewer@1.5.4 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

dlg.viewer@1.5.4
├── @febkosq8/local-save@0.5.1
├── @floating-ui/react@0.27.5
├── @fortawesome/free-regular-svg-icons@6.7.2
├── @fortawesome/free-solid-svg-icons@6.7.2
├── @fortawesome/react-fontawesome@0.2.2
├── @headlessui/react@2.2.0
├── @radix-ui/react-dropdown-menu@2.1.6
├── @rinzai/zen@0.1.10
├── @tailwindcss/forms@0.5.10
├── @tailwindcss/vite@4.0.7
├── @tanstack/match-sorter-utils@8.19.4
├── @tanstack/react-form@1.0.1
├── @tanstack/react-query-devtools@5.67.1
├── @tanstack/react-query@5.67.1
├── @tanstack/react-store@0.7.0
├── @tanstack/react-table@8.21.2
├── @testing-library/jest-dom@6.6.3
├── @testing-library/react@16.2.0
├── @testing-library/user-event@14.6.1
├── @tiptap/extension-bold@2.11.5
├── @tiptap/extension-code@2.11.5
├── @tiptap/extension-color@2.11.5
├── @tiptap/extension-document@2.11.5
├── @tiptap/extension-dropcursor@2.11.5
├── @tiptap/extension-gapcursor@2.11.5
├── @tiptap/extension-hard-break@2.11.5
├── @tiptap/extension-history@2.11.5
├── @tiptap/extension-image@2.11.5
├── @tiptap/extension-italic@2.11.5
├── @tiptap/extension-link@2.11.5
├── @tiptap/extension-list-item@2.11.5
├── @tiptap/extension-paragraph@2.11.5
├── @tiptap/extension-placeholder@2.11.5
├── @tiptap/extension-strike@2.11.5
├── @tiptap/extension-text-style@2.11.5
├── @tiptap/extension-text@2.11.5
├── @tiptap/extension-underline@2.11.5
├── @tiptap/pm@2.11.5
├── @tiptap/react@2.11.5
├── @types/react-dom@19.0.4
├── @types/react@19.0.10
├── @vitejs/plugin-react-swc@3.8.0
├── @vitest/coverage-v8@3.0.8
├── @vitest/ui@3.0.8
├── autoprefixer@10.4.20
├── axios@1.8.2
├── jsdom@26.0.0
├── json-edit-react@1.23.1
├── luxon@3.5.0
├── next-auth@4.24.11
├── postcss@8.5.3
├── react-dom@19.0.0
├── react-dropzone@14.3.8
├── react-error-boundary@5.0.0
├── react-hot-keys@2.7.3
├── react-router-dom@7.3.0
├── react@19.0.0
├── recharts@2.15.1
├── resize-observer-polyfill@1.5.1
├── rollup-plugin-visualizer@5.14.0
├── sass@1.85.1
├── socket.io-client@4.8.1
├── sonner@2.0.1
├── tailwind-scrollbar@4.0.1
├── tailwindcss@4.0.11
├── vite@6.2.1
└── vitest@3.0.8

Answered by jbasko

Mar 12, 2025

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.

View full answer

febkosq8 · 2025-03-07T14:38:01Z

febkosq8
Mar 7, 2025
Author

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.

1 reply

SIRHAMY Mar 9, 2025

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 · 2025-03-12T19:35:10Z

jbasko
Mar 12, 2025

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.

8 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

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

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 2 comments 9 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

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

Uh oh!

Uh oh!

Replies: 2 comments · 9 replies

Uh oh!

febkosq8 Mar 7, 2025 Author

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Replies: 2 comments 9 replies

febkosq8
Mar 7, 2025
Author