{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/097374d84e6e42f1878a9febf99587e2\" frameborder=\"0\" width=\"1670\" height=\"1252\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1252,"width":1670,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1252,"thumbnail_width":1670,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/097374d84e6e42f1878a9febf99587e2-7a7a0815c56130d4.gif","duration":204.818,"title":"How to configure SonarLint with Cursor/VSCode","description":"- Add Node.js path to VS Code settings:\n\"sonarlint.nodejsPath\":\"/Users/mac/.nvm/versions/node/v22.15.0/bin/node\"\n\n- Clear corrupted SonarLint cache:\nrm -rf ~/.sonarlint\n\n- Restart VSCode/Cursor\n- Reconnect to SonarQube using SonarQube: Connect to SonarQube Server\n\nThe core issue was the missing Node.js path preventing JavaScript analysis, combined with corrupted cache that needed clearing! :dart:"}