unplugin-auto-import: 360 Import Lines vs +267ms

I rebuilt the same Vue 3 + Vite 7 app two ways: with hand-written imports (382 import lines) and with unplugin-auto-import 20.3 plus unplugin-vue-components 29.2 (22 import lines left). That dropped 360 import statements. Warm production build medians were 940 ms manual versus 1,207 ms with the plugins (+267 ms), same 105 modules transformed.

Short answer: adopt auto-import on Vue apps where composables and shared utils are the noise, and accept a small build tax. Skip it on tiny apps or teams that want every dependency visible at the top of the file. No affiliate links in this post.

What I tested

• Machine: 8 vCPU Intel Xeon / 15 GB RAM shared Linux cloud box, tested 6 Oct 2026 about 00:05–00:10 IST.
• Versions: Vite 7.3.6, Vue 3.5.43, @vitejs/plugin-vue 6.0.9, unplugin-auto-import 20.3.0, unplugin-vue-components 29.2.0, Node 22.20.0. minify: false so transform cost stays visible.
• Fixture: /workspace/bench-auto-import/. 40 utils, 20 composables, 40 single-file components, plus App and main. Manual tree keeps explicit imports; auto tree deletes utils/composables imports from components and all component imports from App.
• AutoImport config: imports: ["vue"], dirs src/composables and src/utils, vueTemplate: true, dts off. Components plugin scans src/components.
• Timing: wall clock around the local Vite binary. One warm-up each, then 7 interleaved rounds swapping the active src tree between manual and auto.
• Findings: import lines 382 → 22 (−360). Warm medians 940 ms vs 1,207 ms (+267 ms, about 28%). Both builds reported 105 modules. Output JS grew from 209.03 kB to 210.88 kB.
• One surprise: the remaining 22 imports were almost all import { ref, computed } from "vue" inside composables, plus createApp/App in main. AutoImport could erase those too; I left them to show a conservative cut.
• Not tested: Nuxt built-in auto-imports, React/Solid presets, dts generation in CI, IDE go-to-definition edge cases, Windows or macOS.

How many imports did auto-import remove?

Tree	Import lines	Components	Utils	Composables
Manual (explicit)	382	40	40	20
Auto (plugins on)	22	40	40	20
Removed	360	—	—	—

Most of the cut was repetitive import { uN } from '../utils/uN' and import { useThingN } from '../composables/...' inside components, plus 40 App-level component imports replaced by the Components plugin. That pairing matches how Vue teams usually adopt this stack; AutoImport alone would not resolve <CompN/> in the template.

For Vue typing and SFC tooling around the same stack, see the vue-tsc / Vue Language Tools 3.3.12 notes.

Does auto-import slow the Vite build?

Run (production, minify off)	Wall median (7)	Modules	JS size
Manual imports	940 ms	105	209.03 kB
AutoImport + Components	1,207 ms	105	210.88 kB
Delta	+267 ms	0	+1.85 kB

Yes, on this fixture. The plugins scan dirs and rewrite unresolved identifiers, so the transform step pays a fixed cost even when the module graph width stays the same. 267 ms is noticeable in a tight local loop and usually fine in CI next to install and test time.

If your pain is bundler choice rather than imports, the Vite vs Parcel and Rolldown vs Rollup posts cover that axis. Unused-export cleanup after adopting auto-import pairs with Knip vs depcheck.

Should you add unplugin-auto-import?

Situation	My pick
Vue 3 app with many shared composables/utils	Yes
Also tired of importing every SFC in App/layouts	Pair with unplugin-vue-components
Tiny prototype under ~15 components	Skip; explicit imports stay clearer
Team rule: every symbol shows its module path	Skip
Already on Nuxt	Use Nuxt auto-imports; do not double-stack
Need generated .d.ts committed for CI editors	Turn dts on and budget the extra file churn

Bottom line: 360 fewer import lines for +267 ms on a 40-component Vite build is a trade I would take on a mid-size Vue app, and refuse on a tiny one where the plugins obscure more than they save. For the broader Vite toolchain pitch, see Vite+ 1.0.

How this was made: I generated matching manual and auto-import Vue trees on the ShopperCove test box, timed interleaved Vite builds, counted import lines with a small script, and kept the JSON; the write-up was drafted with AI help and checked against that output.

Sources

• https://github.com/unplugin/unplugin-auto-import
• https://www.npmjs.com/package/unplugin-auto-import
• https://github.com/unplugin/unplugin-vue-components
• https://vite.dev/guide/
• https://vuejs.org/guide/reusability/composables.html

Related

• https://www.shoppercove.com/blog/vue-language-tools-3-3-12-definemodel-css-modules-october-2026
• https://www.shoppercove.com/blog/vite-vs-parcel
• https://www.shoppercove.com/blog/vite-plus-1-0-unified-toolchain-october-2026
• https://www.shoppercove.com/blog/knip-vs-depcheck
• https://www.shoppercove.com/blog/rolldown-vs-rollup
• https://www.shoppercove.com/blog/swc-vs-esbuild-babel
• https://www.shoppercove.com/blog/lightningcss-vs-postcss
• https://www.shoppercove.com/blog/rspack-vs-webpack