Go to file
Juan Di Toro 6b097e0860 fix: a tiny bit better upload ui 2024-03-29 00:09:14 +01:00
app fix: a tiny bit better upload ui 2024-03-29 00:09:14 +01:00
patches dep: update deps and patches 2024-03-28 16:56:21 -04:00
public intial commit + login screen 2024-03-05 17:56:17 +01:00
.DS_Store intial commit + login screen 2024-03-05 17:56:17 +01:00
.eslintrc.cjs intial commit + login screen 2024-03-05 17:56:17 +01:00
.gitignore chore: remove package lock and ignore it 2024-03-13 17:06:42 +01:00
.prettierrc.json chore: add prettier config 2024-03-13 09:40:45 -04:00
LICENSE chore: update LICENSE 2024-02-14 05:03:41 -05:00
README.md intial commit + login screen 2024-03-05 17:56:17 +01:00
components.json intial commit + login screen 2024-03-05 17:56:17 +01:00
env.d.ts intial commit + login screen 2024-03-05 17:56:17 +01:00
package.json dep: force override tus-js-client version 2024-03-28 17:18:19 -04:00
postcss.config.js intial commit + login screen 2024-03-05 17:56:17 +01:00
tailwind.config.ts Merge branch 'develop' into riobuenoDevelops/dashboard 2024-03-12 16:28:49 -04:00
tsconfig.json intial commit + login screen 2024-03-05 17:56:17 +01:00
vite-env.d.ts refactor: major refactor of the providers and resources to be more dynamic and flexible 2024-03-19 07:20:57 -04:00
vite.config.ts debug: disable minify 2024-03-18 13:02:48 -04:00

README.md

templates/spa

This template leverages Remix SPA Mode and the Remix Vite Plugin to build your app as a Single-Page Application using Client Data for all of your data loads and mutations.

Setup

npx create-remix@latest --template remix-run/remix/templates/spa

Development

You can develop your SPA app just like you would a normal Remix app, via:

npm run dev

Production

When you are ready to build a production version of your app, npm run build will generate your assets and an index.html for the SPA.

npm run build

Preview

You can preview the build locally with vite preview to serve all routes via the single index.html file:

npm run preview

[!IMPORTANT]

vite preview is not designed for use as a production server

Deployment

You can then serve your app from any HTTP server of your choosing. The server should be configured to serve multiple paths from a single root /index.html file (commonly called "SPA fallback"). Other steps may be required if the server doesn't directly support this functionality.

For a simple example, you could use sirv-cli:

npx sirv-cli build/client/ --single