Tim McCarthy
b1a559cf39
- Crew roster bubbles: explicit text color + opaque distinct surface so they're legible and stand out from the page in both themes (the bug was the <button> defaulting to black-on-dark in dark mode). - End-Scene enforcement: unless Dev Mode is on, a scene can't end until every living Pi-Rat has faced a Deep Challenge or the Obstacle List is empty. end_scene_and_transition now returns (ok, msg) and the route surfaces a 400; the Deep sees a ✓/○ challenge-progress badge on each Pi-Rat bubble. 3 new tests cover the gate. - Hand panel: dropped the how-to-play blurb and the title in favor of a low-profile "Your Hand" label. - Bump VERSION to 8 with changelog entry; check off TODO.md Polish items. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Svelte + Vite
This template should help get you started developing with Svelte in Vite.
Recommended IDE Setup
Need an official Svelte framework?
Check out SvelteKit, which is also powered by Vite. Deploy anywhere with its serverless-first approach and adapt to various platforms, with out of the box support for TypeScript, SCSS, and Less, and easily-added support for mdsvex, GraphQL, PostCSS, Tailwind CSS, and more.
Technical considerations
Why use this over SvelteKit?
- It brings its own routing solution which might not be preferable for some users.
- It is first and foremost a framework that just happens to use Vite under the hood, not a Vite app.
This template contains as little as possible to get started with Vite + Svelte, while taking into account the developer experience with regards to HMR and intellisense. It demonstrates capabilities on par with the other create-vite templates and is a good starting point for beginners dipping their toes into a Vite + Svelte project.
Should you later need the extended capabilities and extensibility provided by SvelteKit, the template has been structured similarly to SvelteKit so that it is easy to migrate.
Why include .vscode/extensions.json?
Other templates indirectly recommend extensions via the README, but this file allows VS Code to prompt the user to install the recommended extension upon opening the project.
Why enable checkJs in the JS template?
It is likely that most cases of changing variable types in runtime are likely to be accidental, rather than deliberate. This provides advanced typechecking out of the box. Should you like to take advantage of the dynamically-typed nature of JavaScript, it is trivial to change the configuration.
Why is HMR not preserving my local component state?
HMR state preservation comes with a number of gotchas! It has been disabled by default in both svelte-hmr and @sveltejs/vite-plugin-svelte due to its often surprising behavior. You can read the details here.
If you have state that's important to retain within a component, consider creating an external store which would not be replaced by HMR.
// store.js
// An extremely simple external store
import { writable } from 'svelte/store'
export default writable(0)