Change:
context.subscriptions.push(workspace.onDidChangeTextDocument((e) => { invalidateHoverScriptsCache(e.document); })); <ins> const isEnabled = () => workspace.getConfiguration('npm').get<boolean>('scriptHover', true); this.enabled = isEnabled(); context.subscriptions.push(workspace.onDidChangeConfiguration((e) => { if (e.affectsConfiguration('npm.scriptHover')) { this.enabled = isEnabled(); } })); </ins> } public provideHover(document: TextDocument, position: Position, _token: CancellationToken): ProviderResult<Hover> { <ins> if (!this.enabled) { return; } </ins> let hover: Hover | undefined = undefined; if (!cachedDocument || cachedDocument.fsPath !== document.uri.fsPath) {

Discussion:
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --When editing quickly in the it's easy to accidentally hit a popup that VS Code recently seems to have introduced to start a debugger or execute a script. This happened to me a lot and it's not only disturbing the workflow but also is prone to errors when accidentally hit. Working fast this is very unwanted behaviour for me as it executes stuff I don't like to be executed with all problems involved. ! I've searched everywhere on how to turn this off, but can't find anything on this feature. I also posted a question on stackoverflow, but there doesn't seem to be a way to turn this behaviour off. Please add a setting to turn this feature off!!
These are called codelenses. Please search settings for
I did, and found this (see screenshot below), but when setting it to 'never' it doesn't turn off (neither after restarting VS Code): ! So I figured that was a different thing. But it could as well be a bug then? [edit] BTW, I also tried this setting on 'off', but same thing, didn't help: ! Somebody on stackoverflow found this commit () , which looks like some settings were removed, but it looks like that one is from way back (2018), and this issue only started appearing recently, so it must be changed in one of recent commits
Please use the Start Extension Bisect command to investigate which extension is adding the two CodeLens items shown in your original screenshot.
Forget that suggestion. I misinterpreted your original screenshot. What you are seeing is on the hover tip, and comes from here: Back in 2018 apparently moved these from CodeLenses to hover links in but didn't retain the configuration setting. The setting I originally pointed you to is checked by code last touched by in February 2021 on Perhaps some rationalization is needed.
This hover has been there for at least 4 years since when I joined the team. There's no setting to turn this off right now as far as I know. PR's welcome for this
<!-- -96bd-47a8-a0e8- --This feature request is now a candidate for our backlog.

The community has 60 days to the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our . Happy Coding!
Hi Connor, thanks for your reply. Just out of interest, what is this setting then if this is not the one?: To me it looks like exactly what I'm after, but isn't working, but is it? !
! ! ! This setting controls the CodeLens run/debug actions.
Not sure why gave this a like. As written in my posts above that's the exact same setting I already tried several times by switching it to 'never'. But it doesn't turn the behaviour off. Neither after a restart of VS Code. The popup keeps coming when hovering over the scripts. So as stated above this is either a bug (see above post about the commit that might have removed this?) or this setting is meant to do something else, which I would find pretty confusing if that would be the case, looking at the description. [edit] it puts this in the , but doesn't seem to do anything:
It only controls the CodeLens, not the hover tooltip, as the description stated. Currently there is no settings to turn the hover tooltip off, thus this issue is turned into a FR.
Yeah, I just see it controls this little guy in the ! Wich is unfortunately not the thing I addressed. Not sure what your point was by posting what I already posted, but hey, we're having some fun ;) Hope the FR will make it to add a setting to remove the unwanted hover. Have a nice day
I take this issue as we want a new configuration parameter that controls the hover tooltip actions. If so, please let me know to submit a PR.
Yes, that sounds accurate. Note this should be grouped under settings rather than since functionality is provided by the npm extension for that. (Yes, we should probably move over code lenses there now that js-debug is built-in, too...)
I've just submitted a PR. Could you please review the PR? However, I made the changes in the extension and didn't move anything to the extension.
Thanks ! Very nice to be able to turn this off now!