Please rebase Cursor’s VS Code fork to ≥ 1.110 (or document timeline) — SCSS/CSS if(sass(…)) breaks built-in validation

Ideas Feature Requests
,
1

Feature request for product/service

Cursor IDE

Describe the request

Hi Cursor team,

I’m hitting a concrete editor regression that is already fixed in stock VS Code but still reproduces in Cursor because of the older embedded VS Code / vscode-css-languageservice stack.

What I’m doing
Using Dart Sass’s CSS-compatible if() with a sass(…) condition, as documented by Sass (Plain-CSS if()), for example:

$base-name: if(
  sass($selector-prefix == ''): 'divider';
  else: '#{$selector-prefix}-divider'
);

What happens in Cursor
The built-in SCSS/CSS validator reports parse errors (e.g. “) expected”, “{ expected”, “at-rule or selector expected”). The code compiles fine with the toolchain (e.g. Angular/nx build), so this is editor validation only, not a Sass bug.

What upstream did
Microsoft fixed this in vscode-css-languageservice ≥ 6.3.10 (see PR #472), which shipped with VS Code 1.110 (February 2026 release notes).

What I see in Cursor
Help → About / %LOCALAPPDATA%\Programs\cursor\resources\app\product.json → vscodeVersion is still ~1.105.x, so the built-in service hasn’t picked up that parser yet. Other editors on a current VS Code base (e.g. Windsurf) don’t show the squiggles for the same file.

Ask

  1. Can you share whether a rebase to VS Code 1.110+ is on the roadmap, with a rough timeline?
  2. Until then, is scss.validate: false the only supported mitigation, or is there another official workaround?

A clearer stance here would help teams that are migrating off deprecated Sass if() and don’t want to disable validation repo-wide.

Thank you!

Cursor Details (from Help → About)

Version: 3.1.0-pre.25.patch.0 (user setup)
VSCode Version: 1.105.1
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0

OS: Windows 11 25H2

Operating System (if it applies)

Windows 10/11