This happened yesterday night. So i realised that vscode was not ‘saving’ the updated code that I just wrote. At first I thought that it was an issue from Nodemon, but then I realised that the issue is from VSCODE. after closing vscode and going back to it, I saw these 2 notification(bottom right) telling me that the changes could not be saved and the code were still ‘stuck’ at the previous version.

This happened yesterday night. So i realised that vscode was not ‘saving’ the updated code that I just wrote. At first I thought that it was an issue from Nodemon, but then I realised that the issue is from VSCODE. after closing vscode and going back to it, I saw these 2 notification(bottom right) telling me that the changes could not be saved and the code were still ‘stuck’ at the previous version.

This happened yesterday night. So i realised that vscode was not ‘saving’ the updated code that I just wrote. At first I thought that it was an issue from Nodemon, but then I realised that the issue is from VSCODE. after closing vscode and going back to it, I saw these 2 notification(bottom right) telling me that the changes could not be saved and the code were still ‘stuck’ at the previous version.

This happened yesterday night. So i realised that vscode was not ‘saving’ the updated code that I just wrote. At first I thought that it was an issue from Nodemon, but then I realised that the issue is from VSCODE. after closing vscode and going back to it, I saw these 2 notification(bottom right) telling me that the changes could not be saved and the code were still ‘stuck’ at the previous version.

In a multi-root code-workspace file’s settings block, I have the following watcher exclusion: