<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ --> <!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- Please search existing issues to avoid creating duplicates. --> <!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ --> <!-- Use Help > Report Issue to prefill these. --> - VSCode Version: Version: 1.52.1 Commit: ea3859d4ba2f3e577a159bc91e3074c5d85c0523 Date: 2020-12-16T16:32:10.090Z Electron: 9.3.5 Chrome: 83.0.4103.122 Node.js: 12.14.1 V8: 8.3.110.13-electron.0 - OS Version: Linux x64 5.4.0-62-generic (Linux Mint 19 Cinnamon 64-bit) Steps to Reproduce: 1. Create a NodeJS project: ```bash npm init npm i uuid # probably any lib code newfile.js ``` 2. Type: ```javascript import * as uuid from 'uuid' uuid.v4() ``` 3. Select the `v4` function call, press `F2` to rename it, type `oops`, press `Enter` 4. A new tab will be opened, showing an `index.d.ts` file whose `v4` string was replaced with `oops` There should be an exception for node_modules, probably some warning or blocking, since you shouldn't just rename stuff from there. <!-- Launch with `code --disable-extensions` to check. --> Does this issue occur when all extensions are disabled?: Yes
Activity
jeanp413 commentedon Jan 21, 2021
Created a PR #42434 fixing this
RyanCavanaugh commentedon Dec 3, 2025
Closing language service bugs related to the 6.0 implementation. For more information, see #62827