ESP32-S3 Bench Guide
ESP32-S3 N16R8 bench guide: live pinout, lessons, simulators and the bench log.
Answer real-world JavaScript, CSS, React and HTTP questions, see every correct answer, and watch your rating grow. Free to learn.
EducationSvelte · TypeScriptGitHub @nealhornerOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗A simple CRUD application to help users practice their frontend skills.
Environment variables are managed with Varlock.
.env.schema (committed) declares every variable the app reads: its type,
whether it's required, and whether it's secret. Put your local values in
.env.local (or .env); both are gitignored. Real environment variables, such
as Railway's, always take precedence over files.
npm install
touch .env.local # then fill in the required values from .env.schema
npx varlock load # check your values against the schema
npm run dev
The required values are DATABASE_URL, BETTER_AUTH_SECRET and
BETTER_AUTH_URL. Dev, build and the npm scripts fail with a clear message if
one is missing or invalid.
App code reads values from ENV (import { ENV } from 'varlock/env'), which
is typed from the schema (src/env.d.ts is generated; don't edit it) and keeps
secrets out of browser bundles. Anything that runs app code outside Vite goes
through varlock run -- (see the start, preview, db:* and script
commands in package.json).
Create migration
npm run db:migrate
Seed the database
npm run db:seed
A contrast audit loads every page in light and dark mode. It checks each piece of text against its background (WCAG AA) and, in dark mode, looks for leftover hard-coded light backgrounds. Run it after changing colors or styles:
npm run audit:contrast
It builds and serves the app the same way the e2e tests do, so it needs the
local database. Locally, add PLAYWRIGHT_CHANNEL=chrome to use your installed
Chrome. It prints a report per theme and saves screenshots under
test-results/. Any issue in either theme fails the run. Set
AUDIT_THEMES=dark to audit one theme, or AUDIT_STRICT=dark to report
light-mode issues without failing.
npm run build
Production runs on Railway with @sveltejs/adapter-node, configured in
railway.json. See .env.schema for the environment variables; set them as
Railway service variables. npm run start runs varlock run -- node build,
which validates them at boot.