How shageen376/employee-list-jwt- works
This repository implements a small Express authentication API. Clients reach registration and login routes, which validate credentials, use the User model for account lookup and creation, and return a response or signed JWT. A separate protected products route verifies JWTs before returning placeholder data. The database connection is configured from MONGO_URI. The README is empty; the sampled routes import middleware/auth.js but do not use it, so it is shown as an unconnected component rather than as part of the protected-route flow.
Main entry points: auth.js Auth routes · server.js Express server · authController.js Auth controller · db.js Mongo connection
Components 9
HTTP API
- Express server
server.js - Auth routes
routes/auth.js
Authentication
- Auth controller
controllers/authController.js - JWT verification
utils/jwtUtils.js - Auth middleware
middleware/auth.js
Persistence
- User model
models/User.js - Mongo connection
db.js
Other components
- API client
- MongoDB
Connections 7
- API client → Express server: sends requests
server.js - Express server → Auth routes: mounts routes
server.js - Auth routes → Auth controller: handles registration and login
routes/auth.js - Auth routes → JWT verification: verifies protected requests
routes/auth.js - Auth controller → User model: looks up and saves
controllers/authController.js - Mongo connection → MongoDB: connects using MONGO_URI
db.js - Auth routes → API client: returns protected data
routes/auth.js