How watwowmap/reactmap works
ReactMap is a Pokémon GO map frontend paired with a Node/GraphQL server. Users browse map overlays and filters; the frontend requests data from GraphQL, whose resolvers obtain records through multi-source database management and domain models. Separate branches cover authentication, scanner capabilities, geocoding, event-derived availability, and Poracle webhook management. The README documents broad overlay and backend support; several subsystem links are therefore omitted or marked unverified where sampled source does not establish the wiring.
Main entry points: resolvers.js Query resolvers · DbManager.js Source manager · QueryData.jsx Map data view · EventManager.js Availability and events
Components 22
Map client
- React app
src/App.jsx - Map data view
src/pages/map/components/QueryData.jsx - Map overlays
src/features - Overlay filters
src/features/drawer - Browser preferences
src/store/useStorage.js - Webhook management UI
src/features/webhooks/hooks/useGetWebhookData.js - Apollo client
src/services/apollo/index.js
GraphQL API
- GraphQL server
server/src/graphql/server.js - Query resolvers
server/src/graphql/resolvers.js
Data and domain
- Source manager
server/src/services/DbManager.js - Map domain models
server/src/models
Integrations
- Authentication strategies
server/src/strategies - Poracle webhook service
server/src/services/Poracle.js - Scanner capabilities
server/src/services/scannerApi.js - Geocoding service
server/src/services/geocoder.js
Runtime services
- Availability and events
server/src/services/EventManager.js - Shared runtime state
server/src/services/state.js - File cache
server/src/services/cache.js
Other components
- Map user
- Scanner backends
- SQL databases
- Poracle service
Connections 25
- Map user → React app: uses
README.md - React app → Map data view: loads
src/App.jsx - Map data view → Map overlays: renders
- Overlay filters → Browser preferences: updates
- Map data view → Browser preferences: reads
- Map data view → Apollo client: queries
- Webhook management UI → Apollo client: queries
- Webhook management UI → Browser preferences: updates
src/features/webhooks/hooks/useGetWebhookData.js - Apollo client → GraphQL server: sends requests
- GraphQL server → Query resolvers: registers
server/src/graphql/server.js - Query resolvers → Source manager: queries data
server/src/graphql/resolvers.js - Query resolvers → Poracle webhook service: uses
server/src/graphql/resolvers.js - Query resolvers → Geocoding service: uses
server/src/graphql/resolvers.js - Query resolvers → Scanner capabilities: uses
server/src/graphql/resolvers.js - Source manager → Map domain models: binds models
server/src/services/DbManager.js - Source manager → Scanner backends: queries sources
- Map domain models → SQL databases: reads records
- Shared runtime state → Source manager: creates
server/src/services/state.js - Shared runtime state → Availability and events: creates
server/src/services/state.js - Shared runtime state → File cache: uses
server/src/services/state.js - Availability and events → Source manager: refreshes availability
server/src/services/EventManager.js - Availability and events → Poracle webhook service: uses
server/src/services/EventManager.js - Availability and events → File cache: loads event cache
server/src/services/EventManager.js - Authentication strategies → Shared runtime state: configured by
server/src/services/state.js - Poracle webhook service → Poracle service: sends requests
server/src/services/Poracle.js