vendure-ecommerce/vendure v3.2.0 on GitHub

Vendure v3.2.0 includes the following new features:

New Dashboard Preview

In February we announced that we'll be moving to React as the basis of a brand-new admin dashboard.

The new React-based dashboard is now in alpha preview! This means you can try it out to get a feel for how it will work, and even run in in parallel to the existing Admin UI. Most create, read, update and delete actions are in place, but bear in mind that this version is far from complete and not yet production-ready.

You can try it out for yourself locally:

Install @vendure/dashboard

Create a vite.config.mts file in the root of your project with the following content:

import {vendureDashboardPlugin} from '@vendure/dashboard/plugin';
import {pathToFileURL} from 'url';
import {defineConfig} from 'vite';

export default defineConfig({
  plugins: [
     vendureDashboardPlugin({
         vendureConfigPath: pathToFileURL('./src/vendure-config.ts'),
         adminUiConfig: {apiHost: 'http://localhost', apiPort: 3000},
     }),
   ],
});

Run npx vite from your project root.

Public demo

You can also find a public demo here: https://react.demo.vendure.io/login

username: admin, password: admin

Next steps with the Dashboard

Our next target is a beta release, in around 1 month from now. In this time we'll be concentrating on:

The APIs for extending the dashboard with your own custom functionality
Theming and branding
Internationalization

All major dependencies updated

This release updates all major dependencies:

NestJS v11
Express v5
TypeScript v5.8.2
Angular v19
TypeORM v0.3.21

Performance improvements

These updates include some performance-oriented changes that you can now benefit from:

NestJS 11 features a faster application startup due to a new approach to their internal bootstrap code
TypeORM v0.3.21 includes an improvement to core logic that has been reported to speed up heavy data reads significantly.
With the latest version of Angular, we're now using the esbuild & Vite-based compiler. In our own CI pipeline this speeds up builds by around 50 seconds.

Improvements to the BullMQJobQueuePlugin

For demanding workloads we recommend the use of our BullMQ-based job queue plugin. With this release we now allow you to take advantage of the full range of features that BullMQ offers by allowing you to specify custom job options at the level of the individual job, using the new setJobOptions config function.

For example, you'll now be able to set priority for individual jobs to ensure more critical jobs get processed first.

// Here we want to assign a higher priority to jobs in the 'critical' queue
setJobOptions: (queueName, job) => {
 const priority = queueName === 'critical' ? 1 : 5;
 return { priority };
}

New VerificationTokenStrategy

Verification tokens are used when verifying the identity of new registrations, or when updating a customer's email address or password.

You can now use the new VerificationTokenStrategy to implement custom generation & verification of these tokens to match your exact project requirements. Example use cases include validation using a Redis cache with TTL, storing tokens in a database, using JWTs, and more.

New Shop API queries

Two new queries are now available in the Shop API which allow you to fetch active ShippingMethods & PaymentMethods, without needing an active Order (which is required to use the existing eligiblePaymentMethods and eligibleShippingMethods.

query ActivePaymentMethods {
  activePaymentMethods {
      id
      name
      code
      description
    }
}

query ActiveShippingMethods {
  activeShippingMethods {
      id
      name
      code
      description
    }
}

Japanese translations in the Admin UI

The Admin UI now supports Japanese as a display language!

BREAKING CHANGES

Node v18 is no longer supported. This is because support was dropped in NestJS v11. Node v18 maintenance ends in April 2025, so you should update to a newer version, such as v22.
For NestJS & Express, please see: https://trilon.io/blog/announcing-nestjs-11-whats-new, which covers potential breaking changes if you use certain Nest features which should not affect most Vendure applications.
The TypeScript update is more likely to require some code changes, since TypeScript becomes more precise and capable of finding potential errors with each release.
If you are using the DefaultCachePlugin, then you should generate a migration that adds precision(3) to the expiresAt column. This will only affect cache records so no prod data will be affected by it.

Updating

Update all Vendure packages to v3.2.0 in your package.json file
Update typescript to the latest version
If you have any NestJS packages in your dependencies, update them to the latest versions.
If you are compiling a custom Admin UI, delete any temporary directory created by the compiler
once your project is building, generate a migration if you are using the DefaultCachePlugin.

Changelog

Fixes

admin-ui Fix build error (fbbcc3e)
admin-ui Fix incorrect pagination range (#3404) (1ee2d45), closes #3404
core Avoid variant options combination check on updateProductVariant mutation (#3361) (c820f42), closes #3361
core Fix progress reporting for collection filters job (3976148)
core Use correct precision for CacheItem.expiresAt (12e2db0)

Features

admin-ui Add Japanese UI translations (#3400) (d24964a), closes #3400
common Add exports field to package.json for module resolution (5623c2b)
core Add two new queries to get public payment and shipping methods (1aa75d5)
core Add two new queries to get public payment and shipping methods (5c7fe42)
core Add updateProductVariant mutation (0b854b4)
core Add verification token strategy (#3294) (9375ba2), closes #3294
core Update all major dependencies (#3445) (d376d83), closes #3445
harden-plugin Allow skipping complexity check in Harden Plugin (#3340) (0bef00b), closes #3340
job-queue-plugin Add support for job options Priority (90b5e05)

Perf

core Remove duplicated calls to promotion checks (e3508f3)

New Contributors

@xtul9 made their first contribution in #3309
@Winne4r made their first contribution in #3272
@HerclasNido made their first contribution in #3298
@putermancer made their first contribution in #3320
@c4nzin made their first contribution in #3343
@jhmen made their first contribution in #3351
@flobacher made their first contribution in #3383
@hooooooouzx made their first contribution in #3363
@ankitdev10 made their first contribution in #3288
@kamil-maslowski made their first contribution in #3368
@ApplePedlar made their first contribution in #3400
@jantokic made their first contribution in #3410
@Szbuli made their first contribution in #3440
@Ryrahul made their first contribution in #3365
@apoca made their first contribution in #3325

Full Changelog: v3.1.0...v3.2.0