Renaming files imported with alias/absolute paths does not update the path

[simplenotezy]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.90.2
• OS Version: macOS 14.1.1 (23B81)

Steps to Reproduce:

1. Create a project with alias imports (e.g. setting up a new Nextjs project and configure to use @/ alias imports)
2. Create a new typescript file
3. Import this file, and ensure to import it using your @/ alias
4. Rename the created typescript file
5. The error is that the reference in the import is not updated, and now vscode is complaining it cannot find the file

See this short video:

Untitled.mov

tsconfig:

{
  "compilerOptions": {
    "lib": [
      "dom",
      "dom.iterable",
      "esnext"
    ],
    "allowJs": true,
    "skipLibCheck": true,
    "strict": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "esnext",
    "moduleResolution": "bundler",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "incremental": true,
    "plugins": [
      {
        "name": "next"
      }
    ],
    "baseUrl": "./src",
    "paths": {
      "@/*": [
        "./*"
      ]
    },
  },
  "include": [
    "next-env.d.ts",
    "**/*.ts",
    "**/*.tsx",
    ".next/types/**/*.ts"
  ],
  "exclude": [
    "node_modules"
  ]
}

Possibly related:

• Rename file by renaming on an aliased path #27959
• Typescript absolute import not working on new/renamed files until refreshing project or restart vscode#97135

[simplenotezy]

Update:

• Renaming the src/shared/features/auth/presentation/IsAuthenticated.tsx to src/shared/features/auth/presentation/IsAuthenticated2.tsx file does not update the imports
• If you rename the folder from src/shared to src/goat-cheese VSCode will update the imports
• If you rename file src/lib/common/presentation/layouts/AppLayout/AppLayout.tsx to src/lib/common/presentation/layouts/AppLayout/AppLayout2.tsx it will correctly update the aliased imports

Very odd situation. Reproducible on two different machines/setups running vscode.

[andrewbranch]

I noticed you invoked the rename via a third-party extension called File Utils. If you rename using only VS Code's built-in functionality, do you still experience the issue?

[JJBocanegra]

@andrewbranch I can confirm that it happens also using VS Code's built-in functionality to rename