MAYFEST/RPLACE

IMPORTANT

this is only intended to be run on Linux (including WSL).

it sometimes does not seem to connect to backend due to "CORS Request Blocked." this is probably because VS Code Terminal opened 127.0.0.1 when it's supposed to open localhost, making the cors package think the origin is not allowed.

solution: open http://localhost:5173 manually.

how to setup

npm run setup

how to run

npm start

---

alternatively you can also:

npm run frontend:dev # or just npx vite

and

npm run backend:dev

in two separate process

Releasing

releasing will be automatically done after updating branch release. make sure main is working before merging to release.

Generated files

do NOT touch files inside these 3 directories. they will be overwritten. ./node_modules/ ./tsc-dist/ ./vite-dist/

Hot Reload

Vite (frontend) ... supports hot reload. tsc + express (backend) ... does NOT support hot reload. reload manually.

TODO

• write .env.production for prod env
• fix vite build not working

React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

• @vitejs/plugin-react uses Babel for Fast Refresh
• @vitejs/plugin-react-swc uses SWC for Fast Refresh

Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:

• Configure the top-level parserOptions property like this:

export default {
  // other rules...
  parserOptions: {
    ecmaVersion: "latest",
    sourceType: "module",
    project: ["./tsconfig.json", "./tsconfig.node.json"],
    tsconfigRootDir: __dirname,
  },
};

• Replace plugin:@typescript-eslint/recommended to plugin:@typescript-eslint/recommended-type-checked or plugin:@typescript-eslint/strict-type-checked
• Optionally add plugin:@typescript-eslint/stylistic-type-checked
• Install eslint-plugin-react and add plugin:react/recommended & plugin:react/jsx-runtime to the extends list