Vite & Webpack · question
Question 5 of 95
What's the difference between the `public` directory and the `src/assets` directory in Vite?
← All Vite & Webpack questions
Re-explain
public directory:
- Files are served directly without processing
- Accessed using absolute paths from root (
/favicon.ico)
- Not processed by Vite's build pipeline
- Good for: favicons, robots.txt, manifest files
- Files keep their original names in production
src/assets directory:
- Files are processed by Vite's build pipeline
- Imported in JavaScript/CSS and get hashed filenames
- Can be optimized, compressed, or transformed
- Good for: images, fonts, CSS files used in components
- Benefit from tree-shaking (unused assets are excluded)
Example:
// src/assets - processed and hashed
import logo from './assets/logo.png'
// public - served directly
// Reference as '/logo.png' in HTML
Rewriting in plainer words…
This answer doesn't lend itself to a diagram - it reads best . No credits were charged.
Why there's no diagram: “”
The diagram below the answer is the concept .
Jump to it ↓
What should the new diagram focus on?
How well did you know this?
AI:
Saved in this browser - sign in to keep your review list.
How should your speech become text?
Listening… your words appear above as you speak - tap Stop when you're done.
Recording · cr - tap Stop & transcribe when you're done.
Transcribing with AI…
Voice:
Keep going - a few more words and AI can grade it.
Interview lens
Likely follow-ups, what you can say, and the weak answers to avoid.
Pro · $10/mo
81 of 95 Vite & Webpack answers are in Pro.
Full answers, code samples, and AI explanations that go simpler or deeper. Cancel anytime.
-
Full answers + code
-
AI explanations, simpler or deeper
-
1,000 AI credits / month
-
Cancel anytime