Large Dataset Handling in StackBlitz: Need Guidance on Query Bounding and Pagination
0 reputation · 10 Feb 2024, 21:51 UTC
Large Dataset Handling in StackBlitz
Goal: Efficiently bound queries and paginate a dataset that exceeds typical limits in a StackBlitz project.
Constraints: StackBlitz relies on Monaco’s virtual scrolling for file editing, but it offers no built‑in API for server‑side query limiting. The console pane buffers ~5,000 lines, dropping older logs, and the preview iframe can render only ~10,000 DOM nodes before performance degrades.
Unresolved Decision: How to implement query bounding and pagination within a StackBlitz environment, and whether the platform can accommodate server‑side pagination logic without custom infrastructure.
Key Questions
- Does StackBlitz provide any API or recommended pattern for implementing LIMIT/OFFSET or cursor‑based pagination in a Node.js backend?
- What are the practical limits for console output buffering and how can they be extended or managed?
- Can the preview iframe support virtualized rendering of large tables, and if so, how can it be integrated into a StackBlitz project?