Standalone module

Frontend development and CLI updates

Explore schema validation enhancements and CLI version updates for improved developer workflows.

Ask about this Page
Copy for LLM
View as Markdown

After completing this page, you should be able to:

  • Apply new schema validation properties like format, maxLength, minLength, and maxUsePerPage to control component behavior.

  • Update and maintain the Frontend CLI to ensure compatibility with the latest Node.js versions and features.

  • Understand the CLI version history and identify which updates are critical for your development workflow.

Frontend Development received several enhancements throughout 2025, focusing on component schema validation capabilities and improvements to developer tooling.

Schema enhancements

  • String and text field validation: component schemas gained new validation options for string and text field types, giving you more control over user input in the Studio. You can now define expected formats for values like email addresses, URLs, or hexadecimal color codes (format), set maximum character limits to prevent excessively long entries (maxLength), establish minimum character requirements to ensure adequate content (minLength), and deliver clear validation feedback to Studio users when they enter data that doesn't meet the criteria.
  • Component usage controls: the maxUsePerPage property was introduced for schema structures, giving you control over how frequently a component or component group can be used within a single page version. This property helps maintain consistency and prevents overuse of specific components that might impact performance or design coherence.

Frontend CLI updates

The Frontend CLI received multiple version updates throughout 2025 each bringing improvements and maintaining compatibility with evolving technologies. Note that these updates were specific to the CLI—the Frontend SDK itself did not receive any updates during 2025.

Keep your CLI up-to-date

To update your Frontend CLI to the latest version, see the CLI documentation for the appropriate update commands based on your operating system, whether you're using macOS, Linux, or Windows. Staying updated with CLI versions helps ensure that you have access to the latest features, bug fixes, and compatibility improvements.

Notable CLI version releases

Version 2.4.3 introduced support for Node.js versions 20 and 22. While Node.js version 18 remained supported, it was no longer recommended for new projects. Node.js versions earlier than 18 were deprecated in July 2025, signaling the phasing out of older runtime versions.
Version 2.4.4 focused on bug fixes and improved visibility. A key improvement was enhanced internal logging—when the CLI encounters errors while streaming data from backend extensions, it now logs retry attempts, making it easier to understand what's happening when transient errors occur.
Version 2.5.0 brought two important enhancements. First, Node.js 24 support was added for backend extensions, keeping pace with the latest Node.js releases. Second, the CLI now displays a warning message when a project uses an outdated Node.js version in backend extensions. This warning became particularly relevant as Node.js versions 20 and earlier were deprecated on 1 July 2025.
Version 2.7.0 marked a significant transition aligned with the broader Identity and URL changes. This version replaces the frontastic.io domain in the CLI with studio.frontend.commercetools.com, reflecting the platform's evolution. Importantly, updating to version 2.7.0 is required to use the upcoming Identity service, making this a critical update for teams preparing for that transition.

Test your knowledge