Web Technologies 2026 · BiUH · Lesson 6
Six names, sorted out · the libraries worth knowing · how to choose one
The confusion is fair
Evan You started three of them. Two hosting companies own parts of the rest. The names were not chosen to help you.
By the end of this part, one sentence sorts all six.
Sort by job, not by name
The components you write — .vue files
also: React, Svelte
The dev server on your laptop, and the build that makes plain files
bigger: Vite+
Vue plus pages from folders, a server, server rendering
React's twin: Next.js
Puts the finished site online
also: Vercel, Netlify, GitHub Pages
The three places code runs, from Frameworks: Vite is the build. Nuxt adds the server. Vue is what the browser runs.
Job 1 · write
<script setup> import { ref } from 'vue' const likes = ref(0) </script> <template> <button @click="likes++"> ♥ {{ likes }} </button> </template>
.vue file is one component: script, template, stylevuejs.org · in Chinese: cn.vuejs.orgThe browser cannot open a .vue file. Something has to translate it first — that is job 2.
Job 2 · run and build
A local server at localhost:5173. Save a file and the page updates at once —
no reload, and the data on screen stays.
Translates every .vue file and packs the result into a dist/ folder:
plain HTML, CSS and JavaScript. That folder is what goes online.
Not only for Vue: React, Svelte and Astro projects use Vite too.
vite.dev is just its website — in Chinese: cn.vite.dev.
Job 2, extended
vp create a new project vp dev the dev server (Vite) vp test the tests (Vitest) vp check mistakes, formatting, types vp build the build for going online
Made by VoidZero. Free and open source since version 1.0, September 2026. You will not need it this semester — but newer tutorials start using it.
Job 3 · grow
pages/index.vue → / pages/about.vue → /about pages/blog/[slug].vue → /blog/anything server/api/likes.ts → /api/likes ← runs on the server, never in the browser
npm run devStart with Vue. Reach for Nuxt when you need a server or link previews — not before.
The two names everyone mixes up
Founded 2024 by Evan You to build JavaScript tools: Vite, Vitest, Rolldown, Oxc — and Vite+.
Bought by Cloudflare in June 2026. The tools stay open source.
You never install "VoidZero".
void deploy builds your Vite app, sets up a database and storage,
and puts it on Cloudflare's servers — in one command.
Public since October 2026.
Same job as Vercel, Netlify, GitHub Pages.
Vue itself still belongs to no company. Vite now does — through VoidZero.
Who pays for it? — the question from Frameworks, one level down
| Tool | Owned by | Since |
|---|---|---|
| Vue | no company — a core team, paid by sponsors | — |
| Vite · Vitest · Vite+ · Void | VoidZero → Cloudflare | 2026 |
| Nuxt | NuxtLabs → Vercel | 2025 |
| Next.js | Vercel, from the start | 2016 |
The tools stay free and still deploy anywhere. What the owners want is the step after the build — your hosting. "On someone else's land" applies here too.
All six, in one sentence each
What you need — and when
| Now | Vue and Vite — one command, npm create vue@latest, gives you both ·
Vue DevTools · the Vue (Official) VS Code extension |
| When a project needs it | Vue Router for more than one page · Pinia for shared data · a component library · Nuxt for a server |
| Not this semester | Vite+, Void, Rolldown, Oxc — they work underneath; you never touch them |
Vue · Getting Started sets up the first row.
Part 2 · The toolbox
Don't build every button yourself.
Component libraries, styling, animation, icons — what works well with Vue, and how to tell a living library from a dead one.
Before the names: what kind of library?
Buttons, dialogs and tables that already look finished. Fast to start — but your site looks like the library.
Nuxt UI · Vuetify · PrimeVue · Element Plus
Only the behaviour: focus, keyboard, screen-reader labels. Every pixel of CSS is yours.
Reka UI · Ark UI
A command copies the component's code into your project. You own it, and you change it.
shadcn-vue · Inspira UI
Headless is the hard part done for you: a dropdown that works with a keyboard and a screen reader is weeks of work.
Component libraries · all work with plain Vue + Vite
| Library | Kind | What it is like |
|---|---|---|
| Nuxt UI | styled | 125+ components on Tailwind — all free since v4, and it works without Nuxt |
| shadcn-vue | copy-in | the code lands in your project; Tailwind for the looks |
| Reka UI | headless | the accessible base under Nuxt UI and shadcn-vue — formerly Radix Vue |
| Vuetify | styled | Google's Material Design, complete |
| PrimeVue | styled | 90+ components, several themes — v5 needs a licence key (free for students); v4 is MIT |
| Element Plus | styled | forms, tables, admin pages — from Ele.me |
| Naive UI | styled | complete and easy to re-theme |
| Quasar | styled | components plus a build for mobile and desktop apps |
One library per project. Two libraries means two kinds of button — and twice the download.
Styling · start with what Vue gives you
<script setup> defineProps(['title']) </script> <template> <article class="card"> <h3>{{ title }}</h3> <slot /> </article> </template> <style scoped> .card { padding: 1rem; border: 1px solid #ddd; border-radius: 8px; } h3 { margin-top: 0; } </style>
scoped: this h3 rule cannot touch any other h3 on the site. Built in. | |
| Tailwind CSS | small classes in the HTML: class="p-4 rounded-lg" — under Nuxt UI and shadcn-vue |
| UnoCSS | the same idea, a faster engine — made by a Vue and Vite team member |
| daisyUI | adds ready classes like btn and card on top of Tailwind |
Everything from lesson 3 still holds. A framework changes where CSS lives, not how it works.
Animation · start with what is built in
<script setup> import { ref } from 'vue' const open = ref(false) </script> <template> <button @click="open = !open">Menu</button> <Transition name="fade"> <nav v-if="open"><a href="/">Home</a></nav> </Transition> </template> <style> .fade-enter-active, .fade-leave-active { transition: opacity .3s; } .fade-enter-from, .fade-leave-to { opacity: 0; } @media (prefers-reduced-motion: reduce) { .fade-enter-active, .fade-leave-active { transition: none; } } </style>
nav appears or leaves, Vue adds classes for a moment — you write the CSS<TransitionGroup> does the same for every item in a listtransition property is the one from lesson 3The rule from the useless machine: prefers-reduced-motion removes the movement, never the meaning.
Animation · when CSS is not enough
| Library | What it is for |
|---|---|
| AutoAnimate | one attribute, v-auto-animate — items slide in, out and around a list by themselves |
| Motion for Vue | <motion.div>: gestures, layout, scroll — from the team behind Framer Motion. Package: motion-v |
| GSAP | timelines and scroll effects, the professional standard — free for everyone since 2025, under its own licence |
| Anime.js | small, works with any framework |
| Lenis | smooth scrolling — often paired with GSAP |
| TresJS | 3D: Three.js written as Vue components |
| Inspira UI | copy-in animated components — glowing cards, text effects. Eye candy: use one, not ten |
Reach in this order: a CSS transition → <Transition> → AutoAnimate → a library. Most sites never need the last step.
The small things every site needs
| Library | What it is for |
|---|---|
| Iconify | 200,000+ icons, one component: <Icon icon="mdi:home" /> — this website uses it |
| Lucide | one clean, consistent icon set. Package: @lucide/vue |
| VueUse | 200+ ready-made helpers: mouse position, dark mode, saving to local storage |
| FormKit | forms with labels, errors and validation built in |
| vue-echarts · vue-chartjs | charts — ECharts started at Baidu, Chart.js is the simpler one |
Icons are the one library almost every project ends up with. Pick one set and keep it.
A real example · the site you open every week
| Framework | Nuxt 4 — with Vue 3.5 inside |
| Components | Nuxt UI — styled |
| Styling | Tailwind CSS |
| Icons | Iconify — the mdi: set |
| Hosting | Vercel — which also owns Nuxt |
And this deck uses none of them: one plain HTML file. Choose tools for the job, not for fashion.
Why you check before you install · five real cases, all recent
| You might find | What happened | Use instead |
|---|---|---|
radix-vue | renamed, 2025 | Reka UI |
lucide-vue-next | deprecated on npm | @lucide/vue |
@headlessui/vue | no release since September 2024 — the React version moved on | Reka UI |
@vueuse/motion | no release since March 2025 | motion-v |
primevue 5 | no longer open source — needs a licence key | PrimeVue 4, or another library |
An AI assistant trained a year ago will suggest every package on the left — confidently.
Five minutes on npmjs.com saves a weekend
One library per job. If two do the same thing, you only need one of them.
Where to learn more
| vuejs.org/tutorial | the official interactive tutorial — in Chinese at cn.vuejs.org |
| play.vuejs.org | write a .vue file in the browser, nothing to install |
| vite.dev/guide | what Vite does, in a few pages |
| nuxt.com/docs | when your project needs a server |
| Vue School | video courses — the Vue 3 fundamentals course is free |
| awesome-vue | the community's list of everything else |
The official tutorial is short, free, and correct. Do it before any video course.
Take these with you
<Transition> first.