Last 12 weeks · 0 commits
5 of 6 standards met
Summary Replaces the custom and scripts with — a lean CLI for managing multiple Slidev presentations. This was actually inspired by this repo (mentioned in Prior Art), so it felt right to bring it full circle. What changes: now uses interactive picker (fuzzy matching, sorted by date, title display) uses (progress tracking, incremental builds) Per-deck build scripts simplified from to Removed 4 deps only needed for custom scripts: , , , What stays the same: All deck source code, components, styles, configs (still parses base paths from per-deck build scripts — verified all 35 work) deployment, caching strategy pnpm workspace setup, per-deck dev/export scripts All Slidev features (glow effect, graph addon, magic links, custom components) Net change:** 40 lines added, 138 lines removed across 39 files (mostly simplified per-deck package.json build scripts). What slidev-decks provides over the custom scripts Interactive picker with fuzzy matching (substring, word-boundary, subsequence scoring) Auto-discovery of in both flat () and nested () layouts for resilient batch builds for building subsets () Incremental builds (skips unchanged decks based on file mtime) Progress counter () during batch builds Package manager auto-detection (pnpm, bun, npm, yarn) for a quick overview of all decks Test plan [x] discovers all 35 Slidev decks (2 pre-Slidev PDF-only talks correctly excluded) [x] base path extraction still works for all 35 decks (regex matches new build script format) [ ] launches interactive picker and starts a deck [ ] builds all decks with correct base paths [ ] Netlify deploy produces working URLs at existing paths Note: Obviously this is a PR which was opened against, what I would consider, a source-available repo that is not commonly open for PRs, so feel free to close if you want, no hurt feelings! 😁
Description Hey there, first of all thank you for all the work on vite etc, I really enjoy using it so far and I guess many agree it's the best solution for bundling JS out there, especially with Rolldown coming along. While watching your talk about Vite Devtools on ViteConf 2025 I realized you write (and say) "pesudo" instead of "pseudo" (spoken like "zudo", I guess). I guess things like that happen all the time when mostly reading about stuff and not hearing it pronounced that often. In the end it doesn't really matter, but I just wanted to let you know and I replaced it in your slides. I hope that's okay. Linked Issues Additional context
Repository: antfu/talks. Description: Slides & code for my talks Stars: 365, Forks: 110. Primary language: JavaScript. Languages: JavaScript (81.4%), Vue (12.9%), HTML (2.6%), CSS (2.2%), TypeScript (0.9%). License: AGPL-3.0. Open PRs: 1, open issues: 0. Last activity: 5mo ago. Community health: 85%. Top contributors: antfu, imgbot[bot], bxt, cirolosapio, ntnyq, zzcyes.