medusa
medusa copied to clipboard
medusajs
The world's most flexible commerce platform.
### Package.json file ```JSON { "name": "backend-server7", "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":...
### Package.json file ```JSON { "name": "", "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":...
### Package.json file ```JSON { "name": "@ljb/webshop-backend", "version": "0.0.1", "scripts": { "build": "medusa build", "init": "medusa exec ./src/scripts/init.ts", "start": "medusa start", "dev": "medusa develop", "test": "npm-run-all test:unit", "test:types": "tsc", "test:integration:http":...
### Package.json file ```JSON { "name": "nuxt-app", "private": true, "type": "module", "scripts": { "build": "nuxt build", "dev": "nuxt dev", "generate": "nuxt generate", "preview": "nuxt preview", "postinstall": "nuxt prepare" }, "dependencies":...
This adds a feature flag module. We also have feature flags that are internal to the Core codebase, and they are not touched in this PR. We should, however, see...
### Package.json file ```JSON { "name": "medusa-starter-default", "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":...
## What This PR adds support for the `DB_PORT` environment variable in `@medusajs/test-utils` package, allowing users to configure custom PostgreSQL port for testing environments. ## Why Currently, the test utilities...
**What** Currently, filtering data providing a `deleted_at` value will automatically apply the `withDeleted` flag which in turns remove the default constraint apply to all queries `deleted_at: null`. The problem is...
**What** Fixed a bug in the prepareListQuery function where nested field ordering was not properly building the expected nested object structure. The function was returning flat objects like { "employee.first_name":...
