-
Notifications
You must be signed in to change notification settings - Fork 218
Language Server apparent infinite loop #1399
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
Comments
I thought I had fixed this 🤔 Will take a look! |
@PhilipTrauner Are you sure you're on the latest language server / VSCode extension version? If so can you provide a reproduction project I can clone? |
@thecrypticace will put together an example project in a short while, but until then, some here's more details:
|
@PhilipTrauner Ooooh yep I can reproduce the resolve causing a freeze. Thanks! Can forget about the repro then! |
I plan to get a release out with this fix soon (hopefully today) |
What version of Tailwind CSS are you using?
4.1.8
What operating system are you using?
macOS
Reproduction URL
Describe your issue
when porting the pattern above from Tailwind v3, i noticed that the Tailwind language server became caught in what appears to be an infinite loop.
building (with
postcss
) still succeeds, and does not consume excessive resources.the same behavior does not occur when using a different, non-shadowed, variable name.
if my assumption is correct, and the name shadowing is the root cause here, i would not mind if shadowing was flagged as an error.
The text was updated successfully, but these errors were encountered: