Annoying missing Node.js popup every workspace startup

Please provide

  • Operating system: macOS / Windows
  • IDE name and version: Eclipse IDE for C/C++ Developers 2026-03
  • SonarQube for Eclipse plugin version: 12.0.0.84623
  • Programming language you’re coding in: C/C++
  • Is connected mode used:
    • SonarQube Cloud, SonarQube Server, or SonarQube Community Build? (if one of the latter two, which version?): SonarQube Cloud

And a thorough description of the problem / question:

Since updating to the newest release 12.0 I noticed that the missing Node.js popup is triggered every time I open the workspace. I can’t recall that this was happening before, also not providing an option to silence it from the popup directly. As I’m working with C/C++ only I don’t care for Node.js :smiley:
It is also a degraded UX since it used to only show a small notification on the bottom right corner in case one was opening a file related to SonarJS / Node.js like a JavaScript file with the information like “Hey no Node.js found, cannot analyze file” etc.

Please fix this as this especially blocking when developing plug-ins where a workspace is fired up like every other minute. Otherwise I have to rollback to the latest version where this does not happen :sad_but_relieved_face:

Cheers :pouring_liquid:

Hello @EclipseWizard! Nice to see you :slight_smile: :man_mage:

This popup does not come from us but from our WWD integration, so I don’t think we can do much. It reminded me of this other thread (in which you reacted :), could you check if the solution would work for you?

1 Like

Hey Dam,

I had a Look back at the thread already but This differs as the Eclipse IDE for C/C++ does not come bundled with WWD :thinking:

I will try to check what can be done to get rid of this, maybe this is a prefs entry that could be set by the Plug-in automatically.

Cheers :partying_face::clinking_glasses:

1 Like

Hey Dam,

I’m back and checked that indeed WWD as a whole is not bundled / installed with the Eclipse IDE for C/C++ Developers but the one sub-plugin (org.eclipse.wildwebdeveloper.embedder.node) that we rely on for finding a suitable Node.js installation locally (see HERE).

I checked their code and raised an issue with them about this sub-optimal (strictly speaking highly annoying) behavior and I hope this can be resolved :relieved_face:
If anything must be done on the SLE side, I will probably take over or let you know.

Until then, this can be closed.

Cheers :wine_glass:

1 Like