Editing
Path autocomplete
Editing · 1 min read
When you are typing the name of another file, it offers you the files that are really there.
When you would want it
A mistyped path is a broken import, and the error it causes names the wrong thing surprisingly often. Being offered only files that exist makes the mistake impossible.
Where to find it
- All Features → Path autocomplete
- Turn on or off
- Settings
What you get out of it
- Broken-import-from-typo stops being possible at the point of typing.
- You stop memorising directory layouts - the project itself fills in its own shape.
How to use it, step by step
- Start typing a path in an import, require, or quoted string.
- The real files and folders from your project appear as suggestions.
- Pick one, or type / to descend into a folder and keep going.
- It only offers what exists, so a completed path cannot be wrong.
Why this beats the usual way
Typo'd paths fail loudly only at build time, one step removed. Completing from the actual file tree moves the guarantee to the first keystroke.
Find it in Universal Search
Path autocomplete · Editing