How raghuls42/processnexus works
ProcessNexus is currently a UI foundation, not a working appliance-repair workflow. Its only visible screen displays a readiness placeholder; index.js defines appliance, warranty, payment, job-status, staff, and technician values, but no workflow uses them in the shown source. config.js initializes Firebase Auth and Firestore from environment variables. The available evidence does not show screen routing, authentication flows, persistence operations, or connections between the UI and domain constants.
Main entry points: config.js Firebase initialization · App.jsx Foundation screen
Components 7
User interface
- Foundation screen
App.jsx
Domain values
- Repair constants
index.js
Firebase setup
- Firebase initialization
config.js
Other components
- User
- Cloud Firestore
- Firebase Auth
- Environment config
Connections 4
- User → Foundation screen: views
App.jsx - Environment config → Firebase initialization: provides settings
config.js - Firebase initialization → Cloud Firestore: initializes
config.js - Firebase initialization → Firebase Auth: initializes
config.js