<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/097374d84e6e42f1878a9febf99587e2&quot; frameborder=&quot;0&quot; width=&quot;1670&quot; height=&quot;1252&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1252</height><width>1670</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1252</thumbnail_height><thumbnail_width>1670</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/097374d84e6e42f1878a9febf99587e2-7a7a0815c56130d4.gif</thumbnail_url><duration>204.818</duration><title>How to configure SonarLint with Cursor/VSCode</title><description>- Add Node.js path to VS Code settings:
&quot;sonarlint.nodejsPath&quot;:&quot;/Users/mac/.nvm/versions/node/v22.15.0/bin/node&quot;

- Clear corrupted SonarLint cache:
rm -rf ~/.sonarlint

- Restart VSCode/Cursor
- Reconnect to SonarQube using SonarQube: Connect to SonarQube Server

The core issue was the missing Node.js path preventing JavaScript analysis, combined with corrupted cache that needed clearing! :dart:</description></oembed>