Async VFS Content Writes - What Plugin Authors Need to Know | The JetBrains Platform Blog

IntelliJ Platform has introduced asynchronous Virtual File System (VFS) content writes to improve performance, especially in scenarios involving slow or remote file systems. This change affects how plugin authors should handle file saves and reads, particularly when interacting with external processes or using direct disk access methods like Path, File, or Files. While code using IntelliJ's file APIs can see updates immediately, direct disk access may require an explicit flush of pending VFS writes to ensure the latest content is read. This asynchronous behavior helps reduce freezes during document saves but requires plugin authors to be aware of potential stale reads or flaky tests due to the difference in file system views. The update is enabled by default for files saved from the editor, but not every write operation is async unless explicitly opted in. Plugin developers should audit their code for assumptions related to saveAllDocuments() and consider flushing pending updates when disk visibility is critical.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.