Turning Neovim into a UE5 IDE: File Watching & Architecture Shifts (Weekly Update 2026-01-09)

Source: Dev.to

Polishing the SQLite Migration

Brief work on cleaning up the SQLite migration process.

UNX: Ditching the Cache for a Pure File Tree

The Change

Moved away from the cache‑dependent architecture to a pure file‑tree approach using a custom structure for UNX.

The Benefit

• No reliance on stale data.
• External file additions or deletions (e.g., via Windows Explorer) are reflected immediately without waiting for a cache rebuild.
• Displays only the information necessary for Unreal Engine development, keeping the tree lightweight.

New UNX Features

N Key (Create File)

Create simple files directly in the tree.
Previously, only class wizards could create files; now you can quickly add a corresponding .cpp source for an existing header by pressing N.

R Key (Force Refresh)

Manually force a tree update/redraw.

One Step Closer to an IDE: UEP start

Implemented UEP start (alias: UDEV start_project), replacing the old manual UEP refresh workflow.

• Watches VCS revisions: Detects git changes automatically.
• Monitors files with vim.uv: Uses Neovim’s built‑in Libuv loop to watch the project folder for any file changes.

Result: Changes are detected instantly. The cache updates file‑by‑file in real time, so commands like UEP files always reflect the current project state. No more manual toggling.

Note: To stop background monitoring, run UEP stop (or UDEV stop_project).