Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 Fail to parse Tailwind 4 css file using the prefix function #5360

Open
1 task done
rphlmr opened this issue Mar 15, 2025 · 1 comment
Open
1 task done

🐛 Fail to parse Tailwind 4 css file using the prefix function #5360

rphlmr opened this issue Mar 15, 2025 · 1 comment
Labels
S-Needs triage Status: this issue needs to be triaged

Comments

@rphlmr
Copy link

rphlmr commented Mar 15, 2025

Environment information

CLI:
  Version:                      1.9.4
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  BIOME_LOG_PATH:               unset
  BIOME_LOG_PREFIX_NAME:        unset
  BIOME_CONFIG_PATH:            unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v22.12.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "npm/11.1.0"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 false

Workspace:
  Open Documents:               0

What happened?

When using the new Tailwind 4 import and prefix CSS functions together, the parser and linter fail to parse the file.

Prefix doc: https://tailwindcss.com/docs/upgrade-guide#using-a-prefix

Repro: https://biomejs.dev/playground/?unsafeParameterDecoratorsEnabled=false&allowComments=false&files.main.css=QABpAG0AcABvAHIAdAAgACIAdABhAGkAbAB3AGkAbgBkAGMAcwBzAC8AdQB0AGkAbABpAHQAaQBlAHMALgBjAHMAcwAiACAAcAByAGUAZgBpAHgAKABkAHYAKQA7AAoAQABpAG0AcABvAHIAdAAgACIAdABhAGkAbAB3AGkAbgBkAGMAcwBzAC8AdABoAGUAbQBlAC4AYwBzAHMAIgAgAHAAcgBlAGYAaQB4ACgAZAB2ACkAOwAKAAoAQABwAGwAdQBnAGkAbgAgACIAdABhAGkAbAB3AGkAbgBkAGMAcwBzAC0AYQBuAGkAbQBhAHQAZQAiADsACgA%3D

Expected result

Should not report any error

Code of Conduct

  • I agree to follow Biome's Code of Conduct
@rphlmr rphlmr added the S-Needs triage Status: this issue needs to be triaged label Mar 15, 2025
@siketyan
Copy link
Member

That's not a valid CSS syntax. See also #3195

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-Needs triage Status: this issue needs to be triaged
Projects
None yet
Development

No branches or pull requests

2 participants