Alokai

2.6

Node.js 24 support, commercetools Product Search, and a paired commercetools upgrade

Showing every integration. Set your stack in Preferences and this page hides what isn't yours.

Minorlatest 2.6.0 · 19 Nov 2026Node 20.* || >=22.14.0

Node.js 24 is now supported and new projects start on it, while the supported range and your existing projects stay as they are. On commercetools, the Unified API package is a major release because it now requires the new API package release exactly. Move the two together. Projects on commercetools that can't activate Product Projection Search can now serve listings from Product Search.

Highlights

Node.js 24 is supported, and new projects and deployed images use it

OptionalCLI & tooling@alokai/cli@vsf-enterprise/storefront-cli
Why:

Node.js 20 has reached its end of life and Alokai will stop supporting it soon. Earlier CLI versions also couldn't compose a store on Node.js 24.

Node.js 24 is now a tested runtime. The supported range stays 20.* || >=22.14.0. Newly generated projects pin Node.js 24.22.3 in .nvmrc, which their CI workflows read. The images store deploy builds for the middleware, Next.js and Nuxt apps use node:24-alpine instead of node:22-alpine. @alokai/cli now composes stores on Node.js 24, where earlier versions failed with TypeError: Cannot read properties of undefined (reading 'replace').

For you:

Your project keeps working on the Node.js version it runs today. Stores you deploy with store deploy run on Node.js 24 from their next deployment, whatever your .nvmrc says. The deploy command has no option to keep the old base image. Moving your own tooling to Node.js 24 is optional, and recommended if you still run Node.js 20.

See the step in the upgrade guide →

All changes by area

Every change in 2.6 has one entry here, grouped by area. The highlights, from above and from the patch sections, are here too, marked with a star. Open an area to see its changes, and open a change to read why it changed and what changed. The upgrade guide from 2.5.6 to 2.6.0 collects the migration steps for the whole line.

CLI & tooling2 changes

added Node.js 24 is supported, and new projects and deployed images use it highlight

Your project keeps working on the Node.js version it runs today, but stores you deploy with store deploy run on Node.js 24 from their next deployment, whatever your .nvmrc says, with no option to keep the old base image. Moving your own tooling to Node.js 24 is optional, and recommended if you still run Node.js 20.

step →
What changed ▸
Why

Node.js 20 has reached its end of life and Alokai will stop supporting it soon. Earlier CLI versions also couldn't compose a store on Node.js 24.

Changed

Node.js 24 is now a tested runtime, and the supported range stays 20.* || >=22.14.0. Newly generated projects pin Node.js 24.22.3 in .nvmrc, the images store deploy builds use node:24-alpine instead of node:22-alpine, and @alokai/cli now composes stores on Node.js 24, where earlier versions failed with TypeError: Cannot read properties of undefined (reading 'replace').

@alokai/cli@vsf-enterprise/storefront-cli

changed The review and Compass CLI plugins are re-released for Node.js 24

If you use either plugin and run on Node.js 24, install the new version. Otherwise you can leave them.

step →
What changed ▸
Why

CLI plugins live in the CLI's own plugin store, not in package.json, so neither the upgrade nor a dependency install moves them.

Changed

@alokai/cli-plugin-review 0.3.2 and @alokai/cli-plugin-compass 1.2.3 are tested on Node.js 24. Their behavior is unchanged.

@alokai/cli-plugin-review@alokai/cli-plugin-compass
commercetoolsAction needed3 changes

added commercetools listings, facets and search can run on Product Search

Nothing changes unless you set searchApi. Switch if your project can't use Product Projection Search or you want to move off it. Storefront code and normalizers need no changes.

step →
What changed ▸
Why

commercetools deprecated Product Projection Search and can't activate it for projects created on or after 2026-09-01. On such projects getFacet, and searchProducts in the Unified API, which uses it, returned errors.

Changed

Setting searchApi: "productSearch" in the integration configuration serves product listings, facets, filters, sorting, text search and category counts from Product Search. The new productSearch option holds the facets and sorting options for that mode. The response of getFacet keeps its shape. Without searchApi, the integration keeps using Product Projection Search.

@vsf-enterprise/commercetools-api@vsf-enterprise/unified-api-commercetools

changed The commercetools Unified API package requires the matching commercetools API package release exactly Action needed

A project that moves one package and leaves the other at its old version holds an unmet peer. Move both to the new versions in the same upgrade.

step →
What changed ▸
Why

@vsf-enterprise/unified-api-commercetools declares @vsf-enterprise/commercetools-api as an exact peer, so the two packages have to move together.

Changed

@vsf-enterprise/unified-api-commercetools 9.0.0 requires @vsf-enterprise/commercetools-api 11.1.0 as its peer, where 8.0.3 required 11.0.3. The major version marks that peer move. It carries no API change of its own.

@vsf-enterprise/commercetools-api@vsf-enterprise/unified-api-commercetools

fixed Algolia product tiles on commercetools show the price in the active currency

Nothing is asked of you. A USD catalogue looks the same as before.

What changed ▸
Why

Product listing and search tiles that come from Algolia always read the USD price, so a catalogue in another currency, such as MYR, showed no price or the wrong one.

Changed

@vsf-enterprise/unified-api-commercetools now reads the price in the request's active currency when it normalizes Algolia product catalog items.

@vsf-enterprise/unified-api-commercetools
Builder.io1 change

changed The Builder.io module targets the v5 SDKs and builds against them

Projects that adopt the module after this release get both changes. A project that already holds the module keeps its own copy and its own SDK versions. If you move @builder.io/sdk-react to a release that requires model, change the model prop in your copy of render-cms-content.tsx to item.model ?? 'page'.

What changed ▸
Why

The Builder.io SDKs the module pinned depend on a native package that doesn't install on Node.js 24. Newer @builder.io/sdk-react releases also made the model prop required, which broke the build of RenderCmsContent.

Changed

The Builder.io module now depends on @builder.io/sdk-react and @builder.io/sdk-vue ^5.4.6, which install on Node.js 24. In render-cms-content.tsx, the Next.js RenderCmsContent component passes model={item.model ?? 'page'}, so a content item with no model uses the page model.

On this page