@vue-storefront/[email protected]

Patch Changes

changed: add eslint-integration rule "class-methods-use-this": "off"

@vue-storefront/[email protected]

Minor Changes

• [ADDED] Logger module

@vue-storefront/[email protected]

Major Changes

rc.2

@vue-storefront/[email protected]

Minor Changes

rc.1

@vue-storefront/[email protected]

Major Changes

Feature logger

@vue-storefront/[email protected]

Patch Changes

• [FIXED] Headers with same name will now have their values merged using the ";' delimiter, rather than ",". This is seen when middleware and defaultRequestConfig set the same header - e.g. Cookie.

After this change, Cookie: vsf-locale=en + Cookie: custom-cookie=123 will result in Cookie: vsf-locale=en; custom-cookie=123, rather than being wrongly separated by ,.

@vue-storefront/[email protected]

Minor Changes

• [CHANGED] defaultMethodsRequestConfig, so the getCategory, and getPage methods will use GET request as a default.

@vue-storefront/[email protected]

Minor Changes

• [CHANGED] defaultMethodsRequestConfig, so the getCategory, and getPage methods will use GET request as a default.

@vue-storefront/[email protected]

Patch Changes

• Updated dependencies:
  • @vue-storefront/[email protected]

@vue-storefront/[email protected]

Major Changes

• [CHANGED][BREAKING] Changed return type of createServer() from Express to Server (from built-in node:http package). Both of those types' interfaces have the .listen() method with the same shape. In some older templates for starting the middleware (middleware.js in your repo) you come across:

async function runMiddleware(app: Express) {

If you're using that older template, please change the Express type to Server:

+ import { Server } from "node:http"
+ async function runMiddleware(app: Server) {
- async function runMiddleware(app: Express) {

• [ADDED] New GET /readyz endpoint for middleware for using with Kubernetes readiness probes. Please see https://docs.alokai.com/middleware/guides/readiness-probes for more information