Path IntelliSense Veyra icon
NEW · FOR VS CODE

Path IntelliSense Veyra

File paths, completed as you type.

Start a path with ./, ../, / or one of your aliases, and see the folders and files that are really there. Imports are written the way your project needs, and paths that don't exist are flagged with a fix.

flightcoders.veyra-path-intellisense · v1.0.0 · Free · MIT · Windows, macOS, Linux

Completing @/assets/ with folders first, images with their sizes and an image preview
FEATURES

Every path, one keystroke away.

Paths everywhere

Imports, require(), HTML src and href, CSS url() and @import, Markdown links, and any string that starts like a path.

Aliases, no setup

@/components from tsconfig or jsconfig paths (following extends), and #utils from package.json imports, read by themselves.

The right import

No extension for bundlers, .js for Node ESM, folders instead of /index: imports written the way your project needs.

Broken paths flagged

“Can’t find ./utils/fromat. Did you mean ./utils/format?” with a one-click fix, resolved the way TypeScript does.

Image previews

See the image and its file size right in the suggestion list before you pick it.

No false alarms

Routes like href="/about", URLs, anchors, template strings and paths still being typed are never flagged.

Public folders

Paths starting with / find files in public/ and static/, like Vite, Next.js and most site tools serve them.

Every language

JavaScript, TypeScript, JSX, Vue, Svelte, Astro, HTML, CSS, SCSS, Less and Markdown, in local, remote and virtual workspaces.

Free and private

MIT licensed, with no account and no telemetry.

A misspelled import path underlined, with the quick fix Change to ./utils/format
A bundler project importing without an extension, and a Node ESM project importing ./db.js
INSTALL

Ready in a minute.

  1. Download the .vsix (22 KB).
  2. In VS Code, press Ctrl+Shift+P and run Extensions: Install from VSIX…, then choose the file.
  3. Type import x from "./ in any file. There's nothing to set up.

Pairs well with Veyra npm IntelliSense, which completes package names. Coming to the Visual Studio Marketplace soon.

Inserted for youVite, Next.js ./components/Header
Node ESM ./db.js
Aliases @/lib/db
read from tsconfig.json
FAQ

Questions

Is it free?

Yes. Path IntelliSense Veyra is free and MIT licensed, with no account and no telemetry.

Do I need to configure my aliases?

No. Aliases in tsconfig.json or jsconfig.json paths (including ones inherited with extends) and in package.json imports are read by themselves. For others, add them to the veyraPath.mappings setting.

Why does it insert .js for my TypeScript files?

Because your tsconfig uses moduleResolution node16 or nodenext. In Node ESM, imports must name the file Node loads after compiling, which is the .js file. Bundler projects get no extension. You can choose yourself with veyraPath.importExtension.

Will it flag my page links as broken?

No. In HTML and Markdown only paths to files, like ./styles/main.css, are checked. Links to pages such as /about are routes, not files, so they are left alone.

Is it the same as the Path Intellisense extension?

It is an independent extension, written from scratch and inspired by the classic Path Intellisense. It adds checks for broken paths, project-aware import extensions, package.json imports and image previews.

More for VS Code: Veyra npm IntelliSense, Veyra Env, Veyra Query Lens for MongoDB and Veyra API Client.

Made by the Veyra team.

Veyra Studio is a fast, free code editor with Live Server, Python debugging and Veyra AI built in.

Download VeyraView on GitHub