A backend like player-backend is needed to provide content.
import from '@/dir_or_filename'
makes is easy to import universal components while inside deeplky nested directories
Change '@'
path in vite.config.ts
Also, I think it's in a config file maybe components.json
. Also find + replace all instances of '@/' to update file imports.
- Find a component on ui.shadcn.com/docs/components
npx shadcn-ui@latest add component-name
- Inside of project root run:
cp env.template .env.development.local
cp env.template .env.production.local
- Prefix every variable with
VITE_
(VITE_SOMETHING=xxx
) - Import with
import.meta.env.VITE_SOMETHING
Vite Documentation on env files.
Instead of NODE_ENV
, use import.meta.env.MODE
by passing vite --mode MODE
at startup.
Note to AVOID passing NODE_ENV=
at startup which can get confusing as documented here.
This project was originally cloned from ariym/base-vite-react.