This is a copy of official Svelte template with added HMR support. It lives at https://github.com/rixo/svelte-template-hot.
This also packages a working eslint configuration and github deploy action (deploys to gh-pages).
This template aims to remain as close to the official template as possible. Please refer to official docs for general usage. For HMR specific stuff, see bellow.
This HMR implementation relies on Svelte's private & non documented API. This means that it can stop working with any new version of Svelte.
Progress of Svelte HMR support can be tracked in this issue.
Update 2020-02-24 We're making progress :)
NOTE This template pins the minor version of Svelte in package.json, using the tilde comparator because, in practice, HMR breakages tend to only happen with new minor versions of Svelte (not patch). And I don't want people to download a hot template with broken HMR... But, in your app, you can change this to your liking -- because you might be more interested in last version of Svelte than stable HMR, or be wise and pin the exact versions of all you dependencies.
yarn build # build app in production
yarn dev:livereload # start a dev server that reloads the app whenever a change is made
yarn dev:nollup # start a dev server that uses hmr to only reload changed portions of app
yarn dev:lan # start a livereload server and make it accessible on local network (useful for running on phone)
yarn dev # alias for yarn dev:nollup
yarn type:check # type-check your app
yarn type:check:watch # type-check your app whenever there is a change to source code
yarn start # serve your app locally
yarn format # format your app
yarn format:check # check your app's formattingTo create a new project based on this template using degit:
npx degit r2dev2/svelte-template-hot svelte-app
cd svelte-app
yarnRun the build script a first time, in order to avoid 404 errors about missing bundle.css in the browser:
yarn buildyarn devNavigate to localhost:5000. You should see your app running. Edit a component file in src, save it, and... Eyeball!
HMR is supported both with Nollup or with Rollup itself with (very experimental) rollup-plugin-hot.
Nollup implements the shortest possible path from a file change to the module reloaded in the browser and is all in-memory. Said otherwise, it is insanely fast. Also, it has been around for some time so it is quite battle tested already.
The Rollup plugin on the other hand is still little more than a proof of concept by now, but it has better sourcemap support and error reporting (according to my own tastes at least).
Support for both Nollup and Rollup HMR is provided by rollup-plugin-svelte-hot. Please report issues regarding HMR in this plugin's tracker. Or this template's project might make more sense. You be the judge.
yarn dev:nollupyarn dev:rollupThis is the default dev of official template.
yarn dev:livereloadNollup HMR is also aliased as dev so you can simply run:
yarn devYou can change the default dev script to your preferred method in the scripts section of package.json.
2020-06-29 Nollup has been made the default dev script (instead of Rollup) because just released Nollup 0.12.0 fixes support for Svelte sourcemaps and dynamic imports, and Nollup is monstrously fast (especially on the most important metrics, that is rebuild time in big projects)!
The suggested workflow is to use Nollup for dev and enjoy instant feedback loop. If you need a plugin that doesn't work with Nollup, or if you are in a situation that Nollup makes harder to debug (mainly because of it running your code through eval), you can fallback on yarn dev:rollup (HMR with rollup-plugin-hot). If you have a bug that you suspect might be caused by HMR or HMR code transform, confirm by turning back to yarn dev:livereload.
yarn build