Edit

E-commerce platform modernization

Note

The Retail Interest Group by Dynamics 365 Commerce has moved from Yammer to Viva Engage. If you don't have access to the new Viva Engage community, fill out this form (https://aka.ms/JoinD365commerceVivaEngageCommunity) to be added and stay engaged in the latest discussions.

This article describes ongoing platform modernization efforts for the Microsoft Dynamics 365 Commerce eCommerce online SDK. These improvements help ensure the SDK remains secure, performant, and aligned with the latest industry standards.

Node.js runtime upgrade

The Dynamics 365 Commerce online SDK now supports Node.js 22. Node.js 22 delivers significant security improvements, an updated V8 engine, and long-term support (LTS) coverage through April 2027.

Supported Node.js versions

Node.js version Support status
Node.js 16.x Supported; deprecation planned
Node.js 18.x Supported; not recommended (reached end of life on April 30, 2025)
Node.js 20.x Supported; not recommended (reached end of life on April 30, 2026)
Node.js 22.x Supported; recommended

Important

  • Support for Node.js 16 will be discontinued in Dynamics 365 Commerce release 10.0.49 (scheduled for July 27, 2026). After this release, Node.js 16 won't be a supported runtime for eCommerce SDK development. We recommend upgrading your development environments to Node.js 22 before this date.

  • Node.js 18 reached end of life on April 30, 2025, and Node.js 20 reached end of life on April 30, 2026. If you're using either of these versions, upgrade to Node.js 22.

For the full Commerce release schedule, see Dynamics 365 Finance, Supply Chain Management, and Commerce public preview releases.

Why upgrade?

Node.js 16 reached end of life on September 11, 2023, Node.js 18 on April 30, 2025, and Node.js 20 on April 30, 2026. These versions don't receive any active security patches. Upgrading to Node.js 22 provides:

  • Active security updates
  • Improved performance through the updated V8 engine
  • Compatibility with the latest SDK dependencies

What you need to do

To prepare for Node.js 16 deprecation, complete the following steps before the Commerce 10.0.49 release:

  1. Upgrade Node.js: Install Node.js 22 in your development environment.

    For installation steps, see Set up a development environment.

    Tip

    If you manage multiple Node.js versions across projects, use Node Version Manager (nvm) to switch between Node.js versions without affecting your other projects.

  2. Reinstall dependencies: After you upgrade Node.js, run yarn install from the root of your SDK repository to apply the compatible dependency set for your new runtime.

    yarn install

  3. Validate your environment: Start the local development server and verify that your modules, themes, and data actions build and run as expected.

    yarn start

TypeScript upgrade

Starting with online SDK package version 9.55 (SDK bootloader version 1.55), the Dynamics 365 Commerce online SDK upgraded its TypeScript compiler from TypeScript 3.x to TypeScript 4.2.4. This upgrade brings improved type checking, better editor tooling support, and access to modern TypeScript language features.

Supported TypeScript version

TypeScript version Support status
TypeScript 3.x No longer supported
TypeScript 4.2.4 Supported (current)

Note

The SDK's package.json resolutions pin the TypeScript version to 4.2.4. After you upgrade to SDK package version 9.55 or later, running yarn install automatically resolves the correct TypeScript version.

What you need to do

If you're upgrading from an SDK version earlier than 9.55, complete the following steps:

  1. Update your SDK package: Upgrade to SDK package version 9.55 or later. For the instructions, see SDK and module library updates.

  2. Reinstall dependencies: Run yarn install from the root of your SDK repository to pick up the updated TypeScript compiler.

    yarn install

  3. Build and fix type errors: Run yarn build and resolve any new TypeScript compilation errors. TypeScript 4.x introduces stricter type checking compared to TypeScript 3.x.

    yarn build

For a full list of changes between TypeScript versions 3.x and 4.x, see the TypeScript release notes.

More resources

  • Last updated on