Skip to content

Commit

Permalink
clarify that the fallback page is created by SvelteKit - closes #3413
Browse files Browse the repository at this point in the history
  • Loading branch information
Rich-Harris committed May 16, 2022
1 parent 79ac9d4 commit e871392
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 1 deletion.
5 changes: 5 additions & 0 deletions .changeset/wise-houses-work.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'@sveltejs/adapter-static': patch
---

Tweak fallback page README
2 changes: 1 addition & 1 deletion packages/adapter-static/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ You can use `adapter-static` to create a single-page app or SPA by specifying a

> In most situations this is not recommended: it harms SEO, tends to slow down perceived performance, and makes your app inaccessible to users if JavaScript fails or is disabled (which happens [more often than you probably think](https://kryogenix.org/code/browser/everyonehasjs.html)).
The fallback page is a blank HTML page that loads your SvelteKit app and navigates to the correct route. For example [Surge](https://surge.sh/help/adding-a-200-page-for-client-side-routing), a static web host, lets you add a `200.html` file that will handle any requests that don't otherwise match. We can create that file like so:
The fallback page is an HTML page created by SvelteKit that loads your app and navigates to the correct route. For example [Surge](https://surge.sh/help/adding-a-200-page-for-client-side-routing), a static web host, lets you add a `200.html` file that will handle any requests that don't otherwise match. We can create that file like so:

```js
// svelte.config.js
Expand Down

0 comments on commit e871392

Please sign in to comment.