A Neovim plugin that suggests import statements by learning from your project's existing imports.
import.nvim is a Neovim plugin that helps developers add import statements faster by learning from their project's existing imports. It searches the codebase for all used imports and presents them in a searchable picker, sorted by frequency, eliminating the need to manually type or copy imports. It solves the problem of repetitive import typing and works especially well when LSP auto-imports are unavailable or ambiguous.
Neovim users working in multi-language projects who frequently add import statements, particularly those in large codebases or using languages where LSP auto-import support is limited.
Developers choose import.nvim because it provides intelligent, context-aware import suggestions based on actual project usage, reducing keystrokes and mental overhead. Its support for multiple pickers, frequency sorting, and extensible language configurations offers a flexible and efficient alternative to manual import management.
An import picker that learns from your codebase
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports Telescope, Snacks, and fzf-lua, allowing users to integrate with their preferred picker, as highlighted in the multiple picker support feature.
Prioritizes imports based on usage frequency across the project, making common selections faster and reducing search time, which is a core part of its philosophy.
Automatically places imports in correct locations for frameworks like Vue and Svelte, such as inside <script> tags, ensuring proper code structure without manual adjustment.
Allows adding custom languages via configuration, with detailed examples for Elm and Vue overrides, making it adaptable to niche or evolving programming environments.
Requires ripgrep for codebase analysis and one of the picker plugins, adding installation and setup overhead that may complicate minimal Neovim setups.
Searching the entire codebase with ripgrep on each use can be slow or resource-intensive, especially in massive projects, potentially delaying import suggestions.
Only suggests imports already used in the project, so new or unused modules won't appear, restricting innovation or adoption of new libraries without manual entry.