Manually define what can be auto imported.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10.5k
- Forks
- 564
- PR merge metrics
- No merged PRs in 30d
Description
Feature Request
I don't like wxt auto-importing certain directories automatically for me. Because it pollutes my ide code suggestion.
What are the alternatives?
Instead please let us define the directories that should be auto imported.
Additional context
I don't mind wxt auto importing its own apis. But I like to import my apis manually, I find it more confortable to be able to see on top, what a certain file depends on.
So, is their any way I can let wxt auto import its own api, but not mine.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by locating WXT's auto-import configuration and the entry point that discovers importable directories; determine how WXT-owned APIs can remain enabled while user API directories are excluded. Done means users can explicitly control those directories and the behavior is covered by relevant tests or documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100