Visual markers are not visible in v2+ in VSCode

[dawidsmuga]

After updating to version v2+, the visual markers no longer appear. I tested both versions 2.0.2 and 2.1.1 with the same result.

Reports are working correctly, but the visual markers were very helpful.

Reverting to version 1.3.4 restores the visual markers and everything works as expected.

Environment:

Visual Studio Code: 1.110.1

[blazejkustra]

What component doesn't work for you? Could you share some code?

What version of react-compiler babel plugin do you use in your project?

Could you check the plugin console output if there are any errors?

[dawidsmuga]

Any components or hooks (tsx, ts).

It's an Expo 55 project where the compiler is built in - I didn't install it manually. I checked node_modules and the version of babel-plugin-react-compiler is 1.0.0.

Like I mentioned before, the same project works fine with extension version 1.3.4.

Plugin console output

2.1.1

[2026-03-08T10:43:16.764Z] CLIENT LOG: react-compiler-marker is being activated!
[2026-03-08T10:43:16.768Z] CLIENT LOG: React Compiler Marker ✨: Commands registered.
[2026-03-08T10:43:16.768Z] CLIENT LOG: React Compiler Marker ✨: Initialization complete.
[2026-03-08T10:43:16.960Z] SERVER LOG: Client connected: Visual Studio Code 1.110.1 (tooltipFormat: markdown, hover: disabled)
[2026-03-08T10:43:16.963Z] CLIENT LOG: React Compiler Marker LSP client started
[2026-03-08T10:43:16.962Z] SERVER LOG: React Compiler Marker LSP Server initialized

1.3.4

[2026-03-08T10:53:20.028Z] LOG: Congratulations, your extension "react-compiler-marker" is now active!
[2026-03-08T10:53:20.028Z] LOG: React Compiler Marker ✨: Commands registered.
[2026-03-08T10:53:20.028Z] LOG: React Compiler Marker ✨: Event listeners registered.
[2026-03-08T10:53:20.139Z] LOG: React Compiler Marker ✨: Initialization complete.

[blazejkustra]

From v2 you need to have inlay hints enabled in vscode for it to work, search for this line in your settings and remove it to verify if this is the issue:

"editor.inlayHints.enabled": "off",

[blazejkustra]

@dawidsmuga @creage @esseguin

If you'd like to keep inlay hints hidden by default but still be able to see the markers on demand, you can use:

"editor.inlayHints.enabled": "offUnlessPressed"

This will show the markers when you hold Ctrl+Option on macOS (or Ctrl+Alt on Windows/Linux).

[creage]

@blazejkustra I have "editor.inlayHints.enabled": "on", but I still don't see markers.

[blazejkustra]

@creage that's surprising, do you have node installed on your system? Can you check logs in your IDE (like above), also anything special about your setup in general? What file are you editing (extension of the file might be useful too) and could you copy paste some sample component that doesn't work?

[creage]

@blazejkustra on v2 I get this:

[2026-03-25T15:44:23.436Z] CLIENT LOG: react-compiler-marker is being activated!
[2026-03-25T15:44:23.440Z] CLIENT LOG: React Compiler Marker ✨: Commands registered.
[2026-03-25T15:44:23.441Z] CLIENT LOG: React Compiler Marker ✨: Initialization complete.
[2026-03-25T15:44:23.722Z] SERVER LOG: Client connected: Visual Studio Code 1.112.0 (tooltipFormat: markdown, hover: disabled)
[2026-03-25T15:44:24.437Z] CLIENT LOG: React Compiler Marker LSP client started
[2026-03-25T15:44:24.435Z] SERVER LOG: React Compiler Marker LSP Server initialized
[2026-03-25T15:44:25.021Z] SERVER ERROR: Failed to load babel-plugin-react-compiler from workspace: Cannot find module '\c%3A\repos\WorkZone\WZONE\node_modules\babel-plugin-react-compiler'

But I have babel-plugin-react-compiler installed:

C:\repos\WorkZone\WZONE>npm list babel-plugin-react-compiler
@wzone/source@2026.0.4 C:\repos\WorkZone\WZONE
├── babel-plugin-react-compiler@1.0.0
└─┬ next@16.2.1
  └── babel-plugin-react-compiler@1.0.0 deduped

I'm on Windows, Node v24.14.0

[creage]

@blazejkustra any updates on that issue?

[blazejkustra]

@creage I don't have access to a Windows machine, maybe you would like to try to fix it yourself?

I feel like this is the main clue: "SERVER ERROR: Failed to load babel-plugin-react-compiler from workspace: Cannot find module '\c%3A\repos\WorkZone\WZONE\node_modules\babel-plugin-react-compiler'"

[creage]

@blazejkustra Never did any extension developing, but from quick debugging, it seems that the workspaceFolders[0].uri needs additional parsing, by removing initial slash char here

react-compiler-marker/packages/server/src/server.ts

Lines 81 to 84 in 6967925

	workspaceFolder = params.workspaceFolders?.[0]?.uri;
	if (workspaceFolder?.startsWith("file://")) {
	workspaceFolder = workspaceFolder.slice(7);
	}

By replacing it with

workspaceFolder = params.workspaceFolders?.[0]?.uri;
if (workspaceFolder?.startsWith("file://")) {
    workspaceFolder = workspaceFolder.slice(7);

    const decoded = decodeURIComponent(workspaceFolder);

    if (decoded.includes(':') && (decoded.startsWith('/') || decoded.startsWith('\'))) {
      workspaceFolder = decoded.slice(1);
    }
  }

P.S. VSCode client side URI instance has fsPath property, which is what we actually need here, but it is different on server side https://stackoverflow.com/a/76337375/1344835

[lklima]

adding "editor.inlayHints.enabled": "on" worked for me in antigravity, @blazejkustra why isn't Antigravity listed as Supported IDEs, this is working fine for me , thanks for this amazing extension 😊

[blazejkustra]

why isn't Antigravity listed as Supported IDEs

No particular reason, I'll add a mention to readme 😄