cube-js/cube

Describe the bug Getting this error when running vitest and angular 22 Error: Directory import '<my_project>\node_modules\fast-deep-equal\es6' is not supported resolving ES modules imported from '<my_project>\node_modules@cubejs-client\ngx\fesm2022\cubejs-client-ngx.mjs Did you mean to import "fast-deep-equal/es6/index.js"? I tried to use resolve.alias, optimizeDeps, inline Deps in vitest config, but with no success. Expected behavior No directory import Version: 1.6.66

Describe the bug Setting CUBEJS_SCHEMA_PATH (or schemaPath) to an absolute path silently loads zero data model files. /cubejs-api/v1/meta returns {"cubes":[]} and there are no errors, warnings, or hints in the cube logs. The cause is in FileRepository: https://github.com/cube-js/cube/blob/master/packages/cubejs-backend-shared/src/FileRepository.ts#L22-L35 public localPath(): string { return path.join(process.cwd(), this.repositoryPath); } protected async getFiles(dir: string, fileList: string[] = []): Promise<string[]> { ... const fullPath = path.join(this.localPath(), dir); await fs.ensureDir(fullPath); files = await fs.readdir(fullPath); path.join (unlike path.resolve) does not treat an absolute argument as a reset point — it just concatenates. Combined with the fs.ensureDir call added in #8909, this means an absolute repositoryPath is silently rewritten to live under process.cwd() and the resulting empty directory is created on disk. No error is thrown. > path.join('/cu

Description The Playground's REST API tab displays the order parameter as an object: "order": { "orders.raw_customers_last_name": "asc", "orders.raw_customers_first_name": "desc" } However, Cube's own documentation recommends the alternative order format (array) for reliable multi-column ordering: "order": [ ["orders.raw_customers_last_name", "asc"], ["orders.raw_customers_first_name", "desc"] ] Why this matters JSON object key order is not guaranteed by RFC 7159. While modern JS engines preserve insertion order, this is implementation-dependent and can break across different languages, parsers, or environments. The REST API tab's purpose is to provide copyable examples for integrators. Showing the object format sets developers up for subtle ordering bugs when they copy it into their applications. Consistency: Issue #7217 already requests that Vue's query builder use the array format. The Playground's REST API tab should follow the same principle. Expected behavior The

Describe the bug When building ClickHouse pre-aggregations with build_range_end that includes milliseconds (e.g., '2026-01-20T23:59:59.999Z'), the generated WHERE clause uses parseDateTimeBestEffort(), which truncates to seconds. This causes the WHERE filter to exclude the intended millisecond boundary. This is critical for any pre-aggregation with time boundaries that need millisecond precision with explicitly set build_range_end to the end of period. To Reproduce Build the pre-aggregation for ClickHouse based Cube Observe the generated WHERE clause uses parseDateTimeBestEffort() instead of parseDateTime64BestEffort() Expected behavior The WHERE clause should use parseDateTime64BestEffort() (or equivalent) to preserve millisecond precision. Version: 1.6.4 (relevant for previous too) Additional context In packages/cubejs-schema-compiler/src/adapter/ClickHouseQuery.ts, the dateTimeCast() method returns parseDateTimeBestEffort() when called without a timezone parameter.