@viu/emporix-sdk@2.33.4

Patch Changes

• #263 bd8d963 Thanks @viu-release-bot! - chore(sdk): sync generated types with upstream Emporix API specs

  Updated services: webhook

@viu/emporix-sdk@2.33.3

Patch Changes

• #261 73f7c23 Thanks @viu-release-bot! - chore(sdk): sync generated types with upstream Emporix API specs

  Updated services: ai-service

@viu/emporix-sdk@2.33.2

Patch Changes

• #259 831c9a7 Thanks @viu-release-bot! - chore(sdk): sync generated types with upstream Emporix API specs

  Updated services: ai-service

@viu/emporix-sdk@2.33.1

Patch Changes

• #257 a333cb2 Thanks @amnael1! - docs: link the changelog from every package README

  npmjs.com renders only a package's README — the registry has no changelog field
  at all, so there is nothing for the website to show. Each README now carries a
  Changelog section pointing at CHANGELOG.md on GitHub, at the copy inside the
  published tarball (served by unpkg), and at the per-version Releases.

  Published as a patch on purpose: npmjs.com shows the README of the published
  version, so a docs-only change that is never released never reaches the page.

  @viu/emporix-mixins also gains README.md, CHANGELOG.md and LICENSE in its
  files array. It listed only dist, and while npm ships a README and a LICENSE
  regardless, it does not ship a CHANGELOG — verified against the published
  tarball, which had no CHANGELOG.md. The link the new section adds would have
  been dead.

@viu/emporix-sdk@2.32.0

Minor Changes

• #252 27623a1 Thanks @amnael1! - feat(sdk): expose response headers to facades

  HttpClient.requestWithMeta returns the parsed body together with the response
  Headers, and PaginatedItems gains optional totalCount, nextCursor and
  prevCursor. Nothing surfaces them yet; this is the groundwork that lets the
  facades read Emporix's X-Total-Count and cursor headers at all.

  RequestOptions.query also widens to accept booleans, so a facade can pass one
  through instead of stringifying it at the call site.

• #254 47570cd Thanks @amnael1! - feat(sdk): opt into absolute match counts on the list facades

  Pass totalCount: true to any list facade to get X-Total-Count back as
  page.totalCount, and an exact hasNextPage instead of the page-size guess.
  Off by default: Emporix computes the count with a second query, so turning it
  on for every list would be a silent cost on every storefront.

  From React the four single-page list hooks accept the same flag — useProducts,
  useProductSearch, useCategories, useCategorySearch. It is part of the query
  key, so a totals request is never served a cached page without them. The
  *Infinite hooks do not offer it: hasNextPage already terminates them.

  Three facades deliberately keep the guess — categories.productsIn,
  segments.listMyProducts and segments.listMyCategories. They page over an
  assignments list and hydrate the hits in a second call, so a total there would
  count assignments rather than the items returned.

• #253 4aa20c0 Thanks @amnael1! - feat(sdk): support cursor pagination on schema custom instances

  listInstances and searchInstances now declare next / prev, return the
  cursors the server sends back, and searchInstances finally forwards
  pageNumber, pageSize and sort — it forwarded none of them and always
  claimed hasNextPage: false, so a search could only ever return the server's
  default first page. New listAllInstances iterates a whole type by cursor.

  Note: searchInstances gained a third query parameter, so a positional auth
  argument moves to fourth.

Patch Changes

• #250 9094d8e Thanks @viu-release-bot! - chore(sdk): sync generated types with upstream Emporix API specs

  Updated services: schema

@viu/emporix-sdk-react@2.33.1

Patch Changes

• #257 a333cb2 Thanks @amnael1! - docs: link the changelog from every package README

  npmjs.com renders only a package's README — the registry has no changelog field
  at all, so there is nothing for the website to show. Each README now carries a
  Changelog section pointing at CHANGELOG.md on GitHub, at the copy inside the
  published tarball (served by unpkg), and at the per-version Releases.

  Published as a patch on purpose: npmjs.com shows the README of the published
  version, so a docs-only change that is never released never reaches the page.

  @viu/emporix-mixins also gains README.md, CHANGELOG.md and LICENSE in its
  files array. It listed only dist, and while npm ships a README and a LICENSE
  regardless, it does not ship a CHANGELOG — verified against the published
  tarball, which had no CHANGELOG.md. The link the new section adds would have
  been dead.

@viu/emporix-sdk-react@2.33.0

Minor Changes

• #255 0bc0307 Thanks @amnael1! - feat(react): accept a host-owned customer token

  customerSession="external" tells EmporixProvider that the customer token was
  handed in by a host application — an Emporix Managed Dashboard module, an
  embedded admin UI. The SDK then never bootstraps a company context from it,
  never attempts a refresh, reports a 401 through onCustomerSessionExpired, and
  treats a changed initialCustomerToken as authoritative.

  Also fixes a latent bug in the default "owned" mode: storage identity no
  longer depends on initialCustomerToken, so delivering a new token stops
  silently discarding cartId, siteCode, language and
  activeLegalEntityId.

  See the Managed Dashboard section in packages/react/README.md and the new
  examples/md-module.

@viu/emporix-sdk-react@2.32.0

Minor Changes

• #254 47570cd Thanks @amnael1! - feat(sdk): opt into absolute match counts on the list facades

  Pass totalCount: true to any list facade to get X-Total-Count back as
  page.totalCount, and an exact hasNextPage instead of the page-size guess.
  Off by default: Emporix computes the count with a second query, so turning it
  on for every list would be a silent cost on every storefront.

  From React the four single-page list hooks accept the same flag — useProducts,
  useProductSearch, useCategories, useCategorySearch. It is part of the query
  key, so a totals request is never served a cached page without them. The
  *Infinite hooks do not offer it: hasNextPage already terminates them.

  Three facades deliberately keep the guess — categories.productsIn,
  segments.listMyProducts and segments.listMyCategories. They page over an
  assignments list and hydrate the hits in a second call, so a total there would
  count assignments rather than the items returned.

@viu/emporix-sdk-next@0.8.2

Patch Changes

• #257 a333cb2 Thanks @amnael1! - docs: link the changelog from every package README

  npmjs.com renders only a package's README — the registry has no changelog field
  at all, so there is nothing for the website to show. Each README now carries a
  Changelog section pointing at CHANGELOG.md on GitHub, at the copy inside the
  published tarball (served by unpkg), and at the per-version Releases.

  Published as a patch on purpose: npmjs.com shows the README of the published
  version, so a docs-only change that is never released never reaches the page.

  @viu/emporix-mixins also gains README.md, CHANGELOG.md and LICENSE in its
  files array. It listed only dist, and while npm ships a README and a LICENSE
  regardless, it does not ship a CHANGELOG — verified against the published
  tarball, which had no CHANGELOG.md. The link the new section adds would have
  been dead.

@viu/emporix-mixins@0.2.1

Patch Changes

• #257 a333cb2 Thanks @amnael1! - docs: link the changelog from every package README

  npmjs.com renders only a package's README — the registry has no changelog field
  at all, so there is nothing for the website to show. Each README now carries a
  Changelog section pointing at CHANGELOG.md on GitHub, at the copy inside the
  published tarball (served by unpkg), and at the per-version Releases.

  Published as a patch on purpose: npmjs.com shows the README of the published
  version, so a docs-only change that is never released never reaches the page.

  @viu/emporix-mixins also gains README.md, CHANGELOG.md and LICENSE in its
  files array. It listed only dist, and while npm ships a README and a LICENSE
  regardless, it does not ship a CHANGELOG — verified against the published
  tarball, which had no CHANGELOG.md. The link the new section adds would have
  been dead.