medusajs/medusa

Package.json file { "name": "@dtc/backend", "version": "0.0.1", "description": "A starter for Medusa projects.", "author": "Medusa (https://medusajs.com)", "license": "MIT", "keywords": [ "sqlite", "postgres", "typescript", "ecommerce", "headless", "medusa" ], "scripts": { "build": "medusa build", "start": "medusa start", "dev": "medusa develop", "lint": "medusa lint", "test:integration:http": "TEST_TYPE=integration:http NODE_OPTIONS=--experimental-vm-modules jest --silent=false --runInBand --forceExit", "test:integration:modules": "TEST_TYPE=integration:modules NODE_OPTIONS=--experimental-vm-modules jest --silent=false --runInBand --forceExit", "test:unit": "TEST_TYPE=unit NODE_OPTIONS=--experimental-vm-modules jest --silent --runInBand --forceExit" }, "dependencies": { "@medusajs/admin-sdk": "2.21.2", "@medusajs/admin-shared": "2.21.2", "@medusajs/caching": "2.21.2", "@medusajs/cli": "2.21.2",

What Medusa version and documentation are you using? v2 Preliminary Checks This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/medusajs/medusa/issues Issue Summary Running yarn prep in a docs project (e.g. www/apps/book) on Windows fails in the edited-dates step. www/packages/build-scripts/src/generate-edited-dates.ts (line 78) runs: `{ git diff --name-only ; git diff --name-only --staged ; } | sort | uniq` through child_process.exec, which uses cmd.exe on Windows. cmd.exe can't parse the { …; } grouping, so the step exits with: '{' is not recognized as an internal or external command, operable program or batch file. code: 255 Environment: Windows 11, Node.js v24.21.0, PowerShell (VS Code terminal), after yarn install and building the packages. Possible second issue in the same function: monorepoRelativePath is derived from path.resolve() and stripped with .replace(/^\//, ""). On Windows that path uses backslashes, while gi

Package and version @medusajs/search-postgres 2.21.2 (latest), Medusa 2.21.2, PostgreSQL 17, keyword search (no vector). What happens A /store/search query with search_options: { typo_tolerance: true, min_score: 0.5, facets: [...] } returns hits and a count that respect min_score, but facet counts that don't. In typo mode the match predicate is ... OR word_similarity(...) > 0.3, so the facets count every product above 0.3, while the hits stop at 0.5. On a catalog of about 10,000 products, the query lavendl (typo for "lavendel") returns 24 hits, all plants, but its option facets include values such as "Verpakking: Bigbag 0,5 m³" that only bagged soil products have. Filtering on one of those values returns 0 hits. For buxsu, 79 of 92 facet counts didn't match the hits a filter on that value returned. Expected The facets are scoped like the hits. The doc comment on buildFacetScope says so: "the filters plus the same match predicate as the hits, so facet counts describe the result set." C

Package.json file { "dependencies": { "@medusajs/dashboard": "2.21.2" } } Node.js version v24.14.0 Database and its version Not applicable: the bug is in admin UI text and happens with any database Operating system name and version Windows 11 Home (10.0.26200) Browser name Chrome What happended? In the admin dashboard, the sort menu for date columns (Created / Updated) shows "Newest first" and "Oldest first", but each option sorts the opposite way. The "Newest first" option sets desc: false (data-table-sorting-menu.tsx in @medusajs/ui). The dashboard sends that as ?order=created_at (transformSortingState in data-table.tsx), and the backend treats an order without - as ASC (get-query-config.ts), which means oldest first. The cause is in en.json: filters.sorting.dateAsc is "Newest first" and filters.sorting.dateDesc is "Oldest first". 33 other locale files copy the same reversed meaning. ar.json is already correct because it uses neutral "ascending/descending" wording. Affected:

Package.json file { "scripts": { "test:integration:http": "TEST_TYPE=integration:http NODE_OPTIONS='--experimental-vm-modules --max-old-space-size=4096' jest --silent=false --runInBand --forceExit" }, "dependencies": { "@medusajs/framework": "2.21.2", "@medusajs/medusa": "2.21.2" }, "devDependencies": { "@medusajs/test-utils": "2.21.2", "@swc/jest": "^0.2.36", "jest": "^29.7.0" } } Excerpt from the project where we found this. The minimal reproduction below needs only [email protected] and [email protected]. Node.js version v22.23.2 and v25.6.0 (minimal reproduction); v25.6.0 (heap snapshot of the Medusa project); v22.23.3 (CI) Database and its version PostgreSQL 18 (postgres:18-alpine) and Redis 7 (redis:7-alpine) in the Medusa project. Neither is needed for the minimal reproduction. Operating system name and version macOS 26.6.2 (arm64) for the minimal reproduction and the heap snapshot. Suite-level heap growth (see Context) was also seen in CI on GitHub Ac