Custom @import Breaks IntelliSense on v4 Beta

[martin-ukhanov]

What version of VS Code are you using?

v1.96.2

What version of Tailwind CSS IntelliSense are you using?

v0.13.64 (pre-release)

What version of Tailwind CSS are you using?

v4.0.0-beta.8

What package manager are you using?

npm

What operating system are you using?

macOS

Tailwind config

N/A

VS Code settings

{
  "workbench.sideBar.location": "right",
  "workbench.iconTheme": "file-icons",
  "window.commandCenter": false,
  "workbench.layoutControl.enabled": false,
  "css.lint.unknownAtRules": "ignore",
  "svelte.enable-ts-plugin": true,
  "editor.quickSuggestions": {
    "strings": "on"
  },
  "editor.tabSize": 2,
  "workbench.startupEditor": "none",
  "git.autofetch": true,
  "tailwindCSS.emmetCompletions": true,
  "editor.formatOnSave": true,
  "editor.defaultFormatter": "esbenp.prettier-vscode",
  "editor.stickyScroll.enabled": false,
  "breadcrumbs.enabled": false,
  "git.enableSmartCommit": true,
  "editor.linkedEditing": true
}

Reproduction URL

https://github.com/martin-ukhanov/tailwind-intellisense-bug

Describe your issue

When using a custom import in the main CSS file (in the reproduction repo I am importing 'test.css' which contains a custom utility class), Tailwind IntelliSense breaks and does not provide suggestions.

[florianbouvot]

@martin-ukhanov I think it's the same issue as #1103, @thecrypticace is working on it #1106.

[martin-ukhanov]

@martin-ukhanov I think it's the same issue as #1103, @thecrypticace is working on it #1106.

@florianbouvot yes I'm aware, @thecrypticace asked me to create this issue in the IntelliSense repo. Not sure if they didn't realize that it was the same.

[thecrypticace]

It is indeed the same problem.

Not sure if they didn't realize that it was the same.

The discussion didn't include many details or a reproduction. Nor did it include an indication of using tsconfig or custom imports just a "… my IntelliSense stopped working out of the blue" so I could not have known it was the same issue.

Closing in favor of #1103

[martin-ukhanov]

It is indeed the same problem.

Not sure if they didn't realize that it was the same.

The discussion didn't include many details or a reproduction. Nor did it include an indication of using tsconfig or custom imports just a "… my IntelliSense stopped working out of the blue" so I could not have known it was the same issue.

Closing in favor of #1103

My apologies, I should have been more clear.

[thecrypticace]

No worries!