vitanovaPackages/README.md

vitanovaPackages

Shared client packages consumed by marketplaces and other projects as npm dependencies.

• packages/auth — @marketplaces/auth. Real implementation. Two independent mechanisms: telegram/ (live QR/session auth for customer + admin) and ed25519/ (challenge/response admin auth, backend not shipped yet).
• packages/payment — @marketplaces/payment. Scaffold only, no implementation yet.

Full consumer documentation lives in the marketplaces repo: docs/PACKAGES-USAGE.md. Rationale: docs/context/adrs/ADR-0001-extract-auth-and-payment-into-shared-marketplaces-packages.md.

Layout

npm workspaces monorepo. Each package builds standalone with tsc to dist/, which is the only thing published (files: ["dist"]).

npm ci
npm run build     # builds all workspaces
npm test          # runs all workspace tests

Angular and rxjs are peerDependencies — the consuming app supplies them, so there is exactly one copy of Angular at runtime.

Making a change

1. Edit under packages/<name>/src, export from index.ts.
2. npx changeset — pick the package and bump type, write one line. CI rejects PRs without one.
3. Open a PR. ci.yml builds, tests, and checks for the changeset.
4. On merge to main, release.yml opens a "Version Packages" PR. Merging that publishes.

Registry — read this before expecting CI to publish

Packages go to a private Verdaccio registry running on the dev server (213.21.246.138, Docker container verdaccio, storage /srv/marketplaces/verdaccio/), not npmjs.

It currently listens on 127.0.0.1:4873 and the server firewall allows only 80/443/SSH — so no CI runner can reach it. release.yml fails loudly at the auth step rather than pretending to succeed. Resolving this needs one of:

• a reverse proxy through the existing nginx (a server-config change, plus TLS — there is no certificate on that box yet), or
• opening the port (plain HTTP with credentials on it — not recommended), or
• moving to a hosted registry entirely.

Until then, publish manually through an SSH tunnel:

ssh -L 4873:127.0.0.1:4873 seto@213.21.246.138

npm login --registry=http://127.0.0.1:4873/ --scope=@marketplaces
npm run build
cd packages/auth && npm publish --registry http://127.0.0.1:4873/

Once reachable, set repo secrets NPM_REGISTRY_URL and NPM_TOKEN and CI takes over.

release.yml/ci.yml use GitHub Actions syntax. Gitea/Forgejo Actions are compatible; other CI systems need translating (same steps: install, build, test, changesets).