Deploy A Single-Page App
Deploy a single-page application (SPA) so direct requests to client-side routes load the application shell.
Prerequisites
Section titled “Prerequisites”Build the application into ./dist. Configure the application to use URL paths and asset URLs that work from the site root.
Add The Application Fallback
Section titled “Add The Application Fallback”-
Keep the main application shell at
dist/index.html. -
Copy the same shell to
dist/200.html. For example, on macOS or Linux:Terminal window cp ./dist/index.html ./dist/200.html -
Deploy the build:
Terminal window buzz deploy ./dist --subdomain my-site -
Open a client-side route directly, such as
https://my-site.buzz.example.com/account.
Buzz first checks for an exact file, an .html file, or a directory index.html. If none exists, it returns 200.html with HTTP status 200. The application’s router then handles the requested path.
The fallback also applies to missing asset paths. A request for an absent script or image can receive the HTML in 200.html with status 200. Confirm that asset URLs point to files included in the build. While 200.html is present, unmatched paths do not reach a custom 404.html page.