themesberg / themesberg/flowbite

Inclusion with TailwindCSS 4.0 results in silent failure on Linux

Open
#1,020 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
9.4k
Forks
862
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

In an existing Tailwind project, following the installation instructions as they exist here and use either @config pointing to a v3 JS config, or the new @plugin format, to include flowbite/plugin.

I specifically did this inside of a OCI container being built on Debian, but I seen other references of this happening on any Linux system. Please note, this issue does not appear to occur on Mac OS (M3).

Expected behavior

Tailwind can compile successfully.

Screenshots
If applicable, add screenshots to help explain your problem.

The error I see when building my container image:
Image

Desktop (please complete the following information): N/A
Smartphone (please complete the following information): N/A
Additional context

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the quickstart installation instructions linked in the issue, then reproduce inclusion through both the @config v3 configuration and the @plugin format in an OCI Debian/Linux environment. Compare the build behavior with macOS and verify that a Tailwind project including flowbite/plugin compiles successfully without the reported silent failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
tailwindcss
Domain
build-system, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.