From 8829182e4aa6dca37a6997a3be9604d09b540288 Mon Sep 17 00:00:00 2001 From: Matt Bierner Date: Mon, 25 Jun 2018 16:25:57 -0700 Subject: [PATCH] Never apply an update path edit that tries doing something with node_modules Root cause is https://github.com/Microsoft/TypeScript/issues/24914 Fixes #52675 --- .../src/features/updatePathsOnRename.ts | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/extensions/typescript-language-features/src/features/updatePathsOnRename.ts b/extensions/typescript-language-features/src/features/updatePathsOnRename.ts index 4e9c0398fea..e1c8ff89069 100644 --- a/extensions/typescript-language-features/src/features/updatePathsOnRename.ts +++ b/extensions/typescript-language-features/src/features/updatePathsOnRename.ts @@ -225,6 +225,12 @@ export class UpdateImportsOnFileRenameHandler { const edits: Proto.FileCodeEdits[] = []; for (const edit of response.body) { + // Workaround for https://github.com/Microsoft/vscode/issues/52675 + for (const change of (edit as Proto.FileCodeEdits).textChanges) { + if (change.newText.match(/\/node_modules\//gi)) { + continue; + } + } edits.push(await this.fixEdit(edit, isDirectoryRename, oldFile, newFile)); } return typeConverters.WorkspaceEdit.fromFileCodeEdits(this.client, edits);