Skip to content

[V4] new import style doesn't work for node_modules in non-standard location (e.g. gradle) #15847

@reubenfirmin

Description

@reubenfirmin

What version of Tailwind CSS are you using?

v4.0.0

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

Gradle, but I've got a reproducible CLI example attached

What version of Node.js are you using?

For example: v9.2.0

What browser are you using?

N/A

What operating system are you using?

Linux

Reproduction URL

https://github.com/reubenfirmin/tailwindv4-import-bug/

Describe your issue

Tailwind v4 style imports do not work when the paths are in non-standard locations for the cli. Tailwind v3 worked fine with this setup.

This folder structure is typical of gradle projects; the input css would likely be in some resources folder, and the node_modules is managed under build/js. The repo above demonstrates the issue.

Metadata

Metadata

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions