hypequery test package for query testing
A command to re-generate types, identify schema drift, smoke test the queries with performance testing and differences. Something like the below: $ npx hypequery test 🔍 Schema Check ✓ All types match database schema ⚠️ New column 'users.deleted_at' detected 🧪 Smoke Test (running queries) ✓ activeUsers (45ms, 12 rows) ✓ revenueByMonth (120ms, 24 rows) ✓ topCustomers (2100ms, 50 rows) 📊 Performance Check ✓ All queries within thresholds ⚠️ topCustomers is slow (2100ms > 1000ms threshold)
Luke 1 day ago
hypequery test package for query testing
A command to re-generate types, identify schema drift, smoke test the queries with performance testing and differences. Something like the below: $ npx hypequery test 🔍 Schema Check ✓ All types match database schema ⚠️ New column 'users.deleted_at' detected 🧪 Smoke Test (running queries) ✓ activeUsers (45ms, 12 rows) ✓ revenueByMonth (120ms, 24 rows) ✓ topCustomers (2100ms, 50 rows) 📊 Performance Check ✓ All queries within thresholds ⚠️ topCustomers is slow (2100ms > 1000ms threshold)
Luke 1 day ago
Streaming query support in serve package
Context Currently only the underlying query builder supports streaming, we need first class support through defineServe. Goal Support for streaming large result sets. Integration with serve package for HTTP streaming responses.
Luke 7 days ago
Streaming query support in serve package
Context Currently only the underlying query builder supports streaming, we need first class support through defineServe. Goal Support for streaming large result sets. Integration with serve package for HTTP streaming responses.
Luke 7 days ago
Completed
Automated Release Pipeline
Context Re-enable automated deployment Goal Re-enable automated releases with Changesets (currently disabled). Set up automated NPM publishing on merge to main, changelog generation, release notes, and pre-release channels (beta, rc).
Luke 7 days ago
Completed
Automated Release Pipeline
Context Re-enable automated deployment Goal Re-enable automated releases with Changesets (currently disabled). Set up automated NPM publishing on merge to main, changelog generation, release notes, and pre-release channels (beta, rc).
Luke 7 days ago
Planned
Production Deployment Guides
Context For successful adoption and deployment Goal Comprehensive deployment guides for Kubernetes (Helm chart), Docker Compose, AWS ECS/Fargate, Vercel Edge, and Cloudflare Workers. Include reference architectures and best practices. Currently NO deployment guides exist.
Luke 7 days ago
Planned
Production Deployment Guides
Context For successful adoption and deployment Goal Comprehensive deployment guides for Kubernetes (Helm chart), Docker Compose, AWS ECS/Fargate, Vercel Edge, and Cloudflare Workers. Include reference architectures and best practices. Currently NO deployment guides exist.
Luke 7 days ago
Migration Tools from Alternatives
Context Enable easier adoption of hypequery from existing tooling Goal Build automated migration tools from Cube.js (data model converter), Metabase (question importer), and custom SQL (translator to query builder). Include side-by-side comparison guides. Lower barrier to adoption.
Luke 7 days ago
Migration Tools from Alternatives
Context Enable easier adoption of hypequery from existing tooling Goal Build automated migration tools from Cube.js (data model converter), Metabase (question importer), and custom SQL (translator to query builder). Include side-by-side comparison guides. Lower barrier to adoption.
Luke 7 days ago
Performance Benchmarks
Context Publish performance benchmarks for comparison Goal Benchmark hypequery performance to raw ClickHouse queries, Cube.js, and custom APIs. Include cache effectiveness analysis, query latency comparisons, and type safety overhead measurements.
Luke 7 days ago
Performance Benchmarks
Context Publish performance benchmarks for comparison Goal Benchmark hypequery performance to raw ClickHouse queries, Cube.js, and custom APIs. Include cache effectiveness analysis, query latency comparisons, and type safety overhead measurements.
Luke 7 days ago
Add dynamic dataset api
Context Users can only currently define standalone queries which limits the following use cases : AI Agents: Can't accurately generate queries based on natural language questions, without a pre-defined query Dashboard Builders: Users can't drag-and-drop dimensions/measures BI Tool Integration: Can't accept dynamic SQL/GraphQL queries Multi-Tenant Custom Views: Each tenant can't define their own metrics Goal Create dynamic API for runtime queries, with a separate entry point to queries. I imagine the API looking something like the below: // generated-datasets.ts (auto-generated) export const datasets = { trips: defineDataset({ table: 'trips', dimensions: { pickup_datetime: dimension.datetime('pickup_datetime'), pickup_date: dimension.date('toDate(pickup_datetime)'), payment_type: dimension.string('payment_type'), // ... all columns from schema }, measures: { count: measure.count(), total_revenue: measure.sum('total_amount'), avg_distance: measure.avg('trip_distance'), // ... common aggregations }, }), } as const; // ===== DYNAMIC QUERIES ===== const dynamicResults = await db.queryDataset(datasets.trips, { dimensions: ['pickup_date', 'payment_type'] as const, measures: ['count', 'total_revenue'] as const, }); // Type: Array // ===== FULLY DYNAMIC (No Type Inference) ===== const aiResults = await db.queryDataset(datasets.trips, parseUserInput(query)); // Type: DynamicQueryResult (Record with metadata) // ===== AI AGENT TOOL GENERATION ===== const tools = db.generateTools(datasets.trips, { mode: 'per-query', // One tool per predefined query // OR mode: 'catalog', // Single tool with dimension/measure selection }); export const api = defineServe({ queries: { // Auto-generated from dataset ...datasets.trips.toQueries(), } });
Luke 7 days ago
Add dynamic dataset api
Context Users can only currently define standalone queries which limits the following use cases : AI Agents: Can't accurately generate queries based on natural language questions, without a pre-defined query Dashboard Builders: Users can't drag-and-drop dimensions/measures BI Tool Integration: Can't accept dynamic SQL/GraphQL queries Multi-Tenant Custom Views: Each tenant can't define their own metrics Goal Create dynamic API for runtime queries, with a separate entry point to queries. I imagine the API looking something like the below: // generated-datasets.ts (auto-generated) export const datasets = { trips: defineDataset({ table: 'trips', dimensions: { pickup_datetime: dimension.datetime('pickup_datetime'), pickup_date: dimension.date('toDate(pickup_datetime)'), payment_type: dimension.string('payment_type'), // ... all columns from schema }, measures: { count: measure.count(), total_revenue: measure.sum('total_amount'), avg_distance: measure.avg('trip_distance'), // ... common aggregations }, }), } as const; // ===== DYNAMIC QUERIES ===== const dynamicResults = await db.queryDataset(datasets.trips, { dimensions: ['pickup_date', 'payment_type'] as const, measures: ['count', 'total_revenue'] as const, }); // Type: Array // ===== FULLY DYNAMIC (No Type Inference) ===== const aiResults = await db.queryDataset(datasets.trips, parseUserInput(query)); // Type: DynamicQueryResult (Record with metadata) // ===== AI AGENT TOOL GENERATION ===== const tools = db.generateTools(datasets.trips, { mode: 'per-query', // One tool per predefined query // OR mode: 'catalog', // Single tool with dimension/measure selection }); export const api = defineServe({ queries: { // Auto-generated from dataset ...datasets.trips.toQueries(), } });
Luke 7 days ago
In Progress
Community Examples Library
Context Help users get started faster with hypequery Goal Create a github repo of hypequery runnable examples to get users up to speed faster. This should include the major use cases: Frontend integration (next, vite) Background jobs and scheduled reports AI agent integration (langchain, ai sdk) Data export APIs Analytics microservices
Luke 7 days ago
In Progress
Community Examples Library
Context Help users get started faster with hypequery Goal Create a github repo of hypequery runnable examples to get users up to speed faster. This should include the major use cases: Frontend integration (next, vite) Background jobs and scheduled reports AI agent integration (langchain, ai sdk) Data export APIs Analytics microservices
Luke 7 days ago
Expand hypequery dev server feature set
Context Improve developer experience Goal Currently the hypequery dev server just provides documentation for the generated endpoints, it would be great to have further features for tracing, observability and debugging. Query list for inspection (raw sql & query builder syntax) and running via a UI to test the output with parameterised inputs Logs showing run query history, completion status, cache status
Luke 8 days ago
Expand hypequery dev server feature set
Context Improve developer experience Goal Currently the hypequery dev server just provides documentation for the generated endpoints, it would be great to have further features for tracing, observability and debugging. Query list for inspection (raw sql & query builder syntax) and running via a UI to test the output with parameterised inputs Logs showing run query history, completion status, cache status
Luke 8 days ago
Caching support in serve package
Context Enable first class caching support in defineServe for better control and logging Goal Currently, caching is managed just at the underlying query builder level, which does not enable observability at the query definition layer. By managing this instead where users defined queries we can improve the management of cache controls, observability and reporting
Luke 11 days ago
Caching support in serve package
Context Enable first class caching support in defineServe for better control and logging Goal Currently, caching is managed just at the underlying query builder level, which does not enable observability at the query definition layer. By managing this instead where users defined queries we can improve the management of cache controls, observability and reporting
Luke 11 days ago
In Progress
Expand documentation of quickstart and recipes
Context Enable users to start using hypequery faster, with no friction Goal Expand the documentation quickstart and recipes sections with the following: Authentication Cron Background jobs Multi-tenancy
Luke 11 days ago
In Progress
Expand documentation of quickstart and recipes
Context Enable users to start using hypequery faster, with no friction Goal Expand the documentation quickstart and recipes sections with the following: Authentication Cron Background jobs Multi-tenancy
Luke 11 days ago