2026-01-18 18:57:06 +04:00
|
|
|
{
|
|
|
|
|
"name": "dexarmarket",
|
|
|
|
|
"version": "0.0.0",
|
|
|
|
|
"scripts": {
|
|
|
|
|
"ng": "ng",
|
|
|
|
|
"start": "ng serve",
|
|
|
|
|
"dexar": "ng serve --configuration=development --port 4200",
|
|
|
|
|
"start:dexar": "ng serve --configuration=development --port 4200",
|
|
|
|
|
"build": "ng build",
|
|
|
|
|
"build:dexar": "ng build --configuration=production",
|
feat(project-editor): add field-schema registry + test harness
Milestone 1 of the Configuration Engine sprint.
- Add schema/ registry: FieldSchema model, SECTION_FIELD_SCHEMAS covering
every editable field per section, and EditorSchemaService (getFields,
getField, all, getByPath). Single source of truth for labels, defaults,
and validator references; sections stay hand-authored (metadata-augmented).
- Stand up Karma + Jasmine (ng test) with a headless, sandbox-free Chrome
launcher; add tsconfig.spec.json, karma.conf.js, angular.json test target,
and npm "test" script. First spec: editor-schema.service.spec (7 passing).
No behavior change. Gate: arch:check, tsc --noEmit, npm test (7/7), build all green.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-17 01:51:13 +04:00
|
|
|
"test": "ng test --watch=false --browsers=ChromeHeadlessNoSandbox",
|
2026-08-06 10:55:00 +04:00
|
|
|
"test:coverage": "ng test --watch=false --browsers=ChromeHeadlessNoSandbox --code-coverage",
|
2026-01-18 18:57:06 +04:00
|
|
|
"watch": "ng build --watch --configuration development",
|
2026-07-03 02:16:03 +04:00
|
|
|
"arch:check:boundaries": "node tools/architecture/check-boundaries.mjs",
|
|
|
|
|
"arch:check:cycles": "npx --yes madge --circular --extensions ts src/app --ts-config tsconfig.app.json",
|
2026-07-10 15:55:38 +04:00
|
|
|
"arch:check": "npm run arch:check:boundaries ; npm run arch:check:cycles",
|
|
|
|
|
"barry": "barry-cache",
|
|
|
|
|
"barry:validate": "barry-cache validate",
|
|
|
|
|
"barry:resume": "barry-cache resume",
|
|
|
|
|
"barry:finalize": "barry-cache finalize",
|
|
|
|
|
"barry:failure": "barry-cache failure"
|
2026-01-18 18:57:06 +04:00
|
|
|
},
|
|
|
|
|
"private": true,
|
|
|
|
|
"dependencies": {
|
fix: install shared packages over git, unbreaking CI
The Verdaccio registry introduced earlier is unreachable from CI (listens on
127.0.0.1:4873 behind a firewall allowing only 80/443/SSH), which broke the
architecture-governance workflow - its npm ci step could no longer resolve
@marketplaces/auth.
Packages are now published to git release branches (release/auth,
release/payment in vitanovaPackages) whose root is the package itself, and
installed with git+<repo>#release/auth. No registry, token, tunnel, or CI
secret - anonymous git read is enough.
- package.json: git dependency; .npmrc removed (no scope mapping needed)
- vitanovaPackages release.yml rebuilt to force-push release branches
- ADR-0001 amended with the distribution change and why the registry lost
- BACKEND-HANDOFF: added the multi-tenancy section (hostname -> tenantKey ->
per-tenant bootstrap config), corrected the install and deploy notes, and
recorded that no CD pipeline exists
- PACKAGE-EXTRACTION / PACKAGES-USAGE rewritten for the git-branch flow
Verified: npm ci, arch:check:boundaries, ng build, 103/103 tests, all with
no credentials configured.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-18 02:08:05 +04:00
|
|
|
"@marketplaces/auth": "git+https://sources.vitanova.network/sdarbinyan/vitanovaPackages.git#release/auth",
|
2026-07-26 19:05:58 +04:00
|
|
|
"@angular/animations": "22.0.8",
|
2026-07-26 19:12:38 +04:00
|
|
|
"@angular/cdk": "22.0.6",
|
2026-07-26 19:05:58 +04:00
|
|
|
"@angular/common": "22.0.8",
|
|
|
|
|
"@angular/compiler": "22.0.8",
|
|
|
|
|
"@angular/core": "22.0.8",
|
|
|
|
|
"@angular/forms": "22.0.8",
|
|
|
|
|
"@angular/platform-browser": "22.0.8",
|
|
|
|
|
"@angular/router": "22.0.8",
|
|
|
|
|
"@angular/service-worker": "22.0.8",
|
2026-01-18 18:57:06 +04:00
|
|
|
"rxjs": "~7.8.0",
|
|
|
|
|
"tslib": "^2.8.0",
|
|
|
|
|
"zone.js": "~0.16.0"
|
|
|
|
|
},
|
|
|
|
|
"devDependencies": {
|
2026-07-26 19:05:58 +04:00
|
|
|
"@angular/build": "22.0.8",
|
|
|
|
|
"@angular/cli": "22.0.8",
|
|
|
|
|
"@angular/compiler-cli": "22.0.8",
|
feat(project-editor): add field-schema registry + test harness
Milestone 1 of the Configuration Engine sprint.
- Add schema/ registry: FieldSchema model, SECTION_FIELD_SCHEMAS covering
every editable field per section, and EditorSchemaService (getFields,
getField, all, getByPath). Single source of truth for labels, defaults,
and validator references; sections stay hand-authored (metadata-augmented).
- Stand up Karma + Jasmine (ng test) with a headless, sandbox-free Chrome
launcher; add tsconfig.spec.json, karma.conf.js, angular.json test target,
and npm "test" script. First spec: editor-schema.service.spec (7 passing).
No behavior change. Gate: arch:check, tsc --noEmit, npm test (7/7), build all green.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-17 01:51:13 +04:00
|
|
|
"@types/jasmine": "~5.1.0",
|
fix(admin): products canDeactivate guard, unblock npm, drop dead deps
RC-01 Phase 1 mechanical fixes (verified against current repo state,
not blindly reapplied from TODO.md):
- admin/products create/edit/duplicate now protected by an unsaved-
changes guard (adminProductDirtyGuard), mirroring the existing
categories pattern. AdminProductsFacade had zero dirty-tracking
before this - added a dirty signal, set true on updateDraft(),
cleared on load/create/successful save. Added confirmLeaveUnsaved
to the adminProducts i18n section (en/ru/hy) - categories already
had its own copy of this key, products didn't.
- barry-cache bumped ^0.1.0 -> ^0.9.3 (the pinned range no longer
resolved on the registry - ETARGET - which had been silently
blocking every npm install/uninstall all cycle).
- Removed primeng/primeicons (npm uninstall, now unblocked) - the
only consumer (items-carousel) was already deleted in RC PERF-01.
- Removed core/search/services/search-history.service.ts, a dead
1-line re-export with zero importers (verified: the real
implementation is features/search/services/search-history.service.ts,
used by search.facade.ts). Left core/search/models/* alone - those
ARE live, imported by catalog components.
Verified before touching: HeaderConfig.showProfile toggle is already
removed from the header-section editor template (TODO.md was stale on
this one) - no change needed, will correct the tracking doc separately.
tsc --noEmit clean, npm run build green (bundle unchanged, primeng
was already tree-shaken out, this just removes the dead dependency
declaration itself).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-25 20:04:51 +04:00
|
|
|
"barry-cache": "^0.9.3",
|
2026-07-26 19:05:58 +04:00
|
|
|
"istanbul-lib-instrument": "^6.0.3",
|
feat(project-editor): add field-schema registry + test harness
Milestone 1 of the Configuration Engine sprint.
- Add schema/ registry: FieldSchema model, SECTION_FIELD_SCHEMAS covering
every editable field per section, and EditorSchemaService (getFields,
getField, all, getByPath). Single source of truth for labels, defaults,
and validator references; sections stay hand-authored (metadata-augmented).
- Stand up Karma + Jasmine (ng test) with a headless, sandbox-free Chrome
launcher; add tsconfig.spec.json, karma.conf.js, angular.json test target,
and npm "test" script. First spec: editor-schema.service.spec (7 passing).
No behavior change. Gate: arch:check, tsc --noEmit, npm test (7/7), build all green.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-17 01:51:13 +04:00
|
|
|
"jasmine-core": "~5.5.0",
|
|
|
|
|
"karma": "~6.4.0",
|
|
|
|
|
"karma-chrome-launcher": "~3.2.0",
|
2026-08-06 10:55:00 +04:00
|
|
|
"karma-coverage": "^2.2.1",
|
feat(project-editor): add field-schema registry + test harness
Milestone 1 of the Configuration Engine sprint.
- Add schema/ registry: FieldSchema model, SECTION_FIELD_SCHEMAS covering
every editable field per section, and EditorSchemaService (getFields,
getField, all, getByPath). Single source of truth for labels, defaults,
and validator references; sections stay hand-authored (metadata-augmented).
- Stand up Karma + Jasmine (ng test) with a headless, sandbox-free Chrome
launcher; add tsconfig.spec.json, karma.conf.js, angular.json test target,
and npm "test" script. First spec: editor-schema.service.spec (7 passing).
No behavior change. Gate: arch:check, tsc --noEmit, npm test (7/7), build all green.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-17 01:51:13 +04:00
|
|
|
"karma-jasmine": "~5.1.0",
|
|
|
|
|
"karma-jasmine-html-reporter": "~2.1.0",
|
2026-07-26 19:05:58 +04:00
|
|
|
"typescript": "~6.0.3"
|
2026-01-18 18:57:06 +04:00
|
|
|
}
|
2026-08-06 10:55:00 +04:00
|
|
|
}
|