-
Notifications
You must be signed in to change notification settings - Fork 1
Installation
| Tool | Minimum version | Notes |
|---|---|---|
| Node.js | 20 | The CI pipeline uses Node 22; both work locally |
| npm | 10 | Bundled with Node 20+ — no separate install needed |
| Git | any | For cloning the repository |
| A modern browser | — | Chrome, Edge, Firefox, or Safari |
| Supabase CLI | latest | Optional — only needed for local Supabase development |
| Docker Desktop | any | Optional — required by the Supabase CLI for local dev, or to run the production container |
Supabase is fully optional. The app works identically without it. See Supabase Sync for setup instructions.
git clone [email protected]:NesiciCoding/RubricMaker.git
cd RubricMakerOr clone over HTTPS if you haven't set up SSH keys:
git clone https://github.com/NesiciCoding/RubricMaker.git
cd RubricMakernpm installThis installs all runtime and development dependencies listed in package.json. The first run takes 1–2 minutes; subsequent runs are faster due to the npm cache.
If you want the Supabase connection form in Settings to be pre-filled, copy the env template:
cp .env.example .env.localThen open .env.local and fill in your Supabase URL and anon key. Leave it blank if you're not using Supabase — the app works fine without it.
npm run devOpen http://localhost:5173 in your browser. The app loads instantly with hot-module replacement — edit a file and the browser updates without a full reload.
If the dev server starts and the app opens in the browser, you're good. To double-check the full toolchain:
npm run typecheck # TypeScript type-check (no output = all good)
npm run lint # ESLint
npm run test # Run the test suiteAll three should complete without errors on a clean install.
Make sure you are on Node 20 or later:
node --version # should print v20.x.x or higherIf you have multiple Node versions installed, use nvm or fnm to switch:
nvm use 20
# or
fnm use 20Either stop the other process or start Vite on a different port:
npm run dev -- --port 5174Open the browser's developer console (F12). A missing module error usually means npm install didn't complete successfully — delete node_modules/ and run it again:
rm -rf node_modules
npm install