Microsoft/vscode

Deleting files with vscode fs api can cause contributed custom text editors to not be able to open subsequent files with the same name

Open

#278883 opened on Nov 21, 2025

View on GitHub
 (0 comments) (0 reactions) (1 assignee)TypeScript (74,848 stars) (10,221 forks)batch import
bugcustom-editorshelp wanted

Description

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

  • VS Code Version: 1.106.2
  • OS Version: Windows_NT x64 10.0.26100

Steps to Reproduce:

Clone this repository: https://github.com/Greglar4/vscodeBugExampleRepository and follow the readme steps, which are:

  1. Open this project in VS Code
  2. Run npm install
  3. Run npm run build
  4. Run the extension in the development host (e.g. by using F5)
  5. Create a file with .fnf extension
  6. Open the file with the File Not Found Example Editor
  7. Ensure the vs code setting Workbench > Editor: Close On File Delete is off.
  8. Press the button that says "Click Me". This will delete the file via vs code fs api.
  9. Without closing the File Not Found Example Editor, close the vs code window which is running the extension in the development host.
  10. Run the extension in the development host (e.g. by using F5)
  11. Close the editor of the file that was deleted in step 8.
  12. Create a .fnf file with the same name as the file created in step 5.
  13. Try to open the file created in step 12 with the File Not Found Example Editor, it will give a file not found error, even though this file now exists, and that the text editor can open the file fine.

Contributor guide

Tech stack
typescriptnodejs
Domain
apidesktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
VS Code extension APICustom text editorsTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Start by cloning the reproduction repository (github.com/Greglar4/vscodeBugExampleRepository) and follow the steps to reproduce the bug. Focus on the custom editor implementation in the extension, specifically how it handles file deletion via the VS Code fs API. Investigate the lifecycle of custom editors in VS Code's source code, particularly around file deletion and re creation with the same URI. Look at how the editor's state is managed when a file is deleted and then re created.