How neocheetahlee-coder/nctdiscography-sub-unit_explorer works
This is a small NCT song-discovery web app. On startup, the server fetches Apple Music results for several NCT units and storefronts, combines and deduplicates them, and builds a search index. A browser can request songs with optional search, unit filtering, and sorting; the API returns the matching songs and a top-three subset. The server also serves the files in public/. The README is empty, and the HTML and CSS contents were not sampled, so their specific UI behavior is unknown.
Main entry points: server.js Songs API · index.html Web page · style.css Page styles
Components 12
Catalog acquisition
- Catalog loader
server.js - Song collection
server.js
Song queries
- Search hash table
server.js - Songs API
server.js - Unit filtering
server.js - Custom sorting
server.js - Top-three selection
server.js
Web delivery
- Express server
server.js - Web page
public/index.html - Page styles
public/style.css
Other components
- Browser user
- Apple Music API
Connections 15
- Express server → Catalog loader: starts loading
- Catalog loader → Apple Music API: requests songs
- Apple Music API → Catalog loader: returns results
- Catalog loader → Song collection: stores deduplicated songs
- Catalog loader → Search hash table: builds index
- Browser user → Express server: requests page or API
- Express server → Web page: serves static file
- Express server → Page styles: serves static file
- Express server → Songs API: routes songs request
- Songs API → Song collection: reads songs
- Songs API → Search hash table: searches keyword
- Songs API → Unit filtering: filters by unit
- Songs API → Custom sorting: sorts results
- Songs API → Top-three selection: selects first three
- Songs API → Browser user: returns JSON