Frontend Development Releases

Version 2.0.0 of the SDK contains breaking changes.

Version 2.0.0 of the commercetools Frontend SDK introduces new features and bug fixes. We recommend upgrading to Version 2.0.0 of the SDK to ensure you get the newest features, improvements, and fixes.

For a step-by-step guide about how to update your SDK version, see the following:

• B2C projects migration guide
• B2B projects migration guide

The new version of the Store Launchpad for B2C Retail contains a new feature, enhanced functionality, and bug fixes.

The new version of the Store Launchpad for B2B Manufacturing contains enhanced functionality and bug fixes.

The new version of the Store Launchpad for B2C Retail contains a new feature, enhanced functionality, and a bug fix.

The new version of the Store Launchpad for B2B Manufacturing contains new features, enhanced functionality, and a bug fix.

The Store Launchpad for B2B Manufacturing contains a new feature, enhanced functionality, and a bug fix

The Adyen integration is now deprecated. If you currently use this integration, it will continue to work as expected. For new commercetools Frontend projects, you can use Adyen as a payment service provider (PSP) by leveraging the payment Connector for Adyen.

The new version of the Store Launchpad for B2C Retail contains enhanced functionality and bug fixes.

The new version of the Store Launchpad for B2B Manufacturing contains new features, enhanced functionality, and bug fixes.

Version 2.4.2 of the CLI fixes the following bugs:

• When the CLI does not detect Yarn, it now provides installation instructions instead of only reporting that Yarn is absent.
• The CLI no longer parses the frontastic binary file as a configuration file when it is present in the execution directory.
• To increase accuracy, the guid validation pattern in the code generator is now stricter.
• Long messages no longer overflow onto the right border of the CLI log view.
• The upload of a backend extension no longer fails on the first invocation of the CLI in a newly cloned repository, which means you no longer need to restart the CLI.

The new version of the Store Launchpad for B2C Retail contains enhanced functionality and bug fixes. The new version of the Store Launchpad for B2B Manufacturing contains enhanced functionality.

The Store Launchpad for B2C Retail underwent some changes to enhance its functionality and user experience.

The Store Launchpad for B2B Manufacturing underwent some changes to enhance the functionality and user experience.

The Store Launchpad for B2C Retail underwent some changes to enhance its functionality and user experience.

The Store Launchpad for B2B Manufacturing underwent some changes to enhance the functionality and user experience.

You can now configure the customHeaderValue option in the commercetools Frontend SDK to send custom header data to backend extensions. You can also set the customHeaderValue option in the API methods.

We've also added a skipQueue option to the callAction API method, which lets you opt out of the action call queue and execute the action asynchronously.

The Store Launchpad for B2B Manufacturing and the Store Launchpad for B2C Retail underwent some changes to enhance the functionality and user experience.

Version 2.4.1 of the CLI removes the versionNumber parameter from the upload command, which is used to upload builds for custom Git repositories. This change is backward compatible and doesn't break any existing workflows that use this parameter. If the parameter is passed, it won't have any effect.

Additionally, we fixed a bug on the upload command where setting the --buildSuccessful or --deploy parameters to false was interpreted as true. For example, the frontastic upload --deploy false command initiated a staging deployment. Now, the parameters work as expected.

We fixed some bugs on the Store Launchpad for B2B Manufacturing to enhance its functionality and user experience.

The Store Launchpad for B2B Manufacturing underwent some changes to enhance its functionality and user experience.

The Store Launchpad for B2C Retail underwent some changes to enhance its functionality and user experience.

The Store Launchpad for B2B Manufacturing contains new and enhanced functionality. Additionally, we fixed some bugs.

commercetools Frontend SDK underwent changes to improve the developer experience and extensibility of the SDK.

We fixed some bugs on the Store Launchpad for B2C Retail to enhance its functionality and user experience.

commercetools Frontend is now compatible with Node.js version 18.x. This ensures that you can work with a version that is still maintained.
Using other versions greater than or equal to 16.14 is still supported but not recommended.

For information on how to make your project compatible with Node.js 18.x, see Backend compatibility with Node.js 18.

The Store Launchpad for B2B Manufacturing now contains new and enhanced functionality designed to improve the experience of buyers and sellers. Additionally, we fixed two bugs on login and registration.

Version 2.4.0 of the CLI introduces a change to project initialization and fixes bugs.

Version 2.3.1 of the CLI fixes two bugs in the frontastic upload command:

• In certain scenarios, the command attempted to initiate the interactive creation of a configuration file. We have corrected this behavior because the command does not require a configuration file and should operate non-interactively, especially in continuous integration environments.
• Running the command without setting either the clientId or clientSecret environment variables failed and generated an ambiguous error message related to token retrieval from Studio. Now, the error message is clearer and states which variables are missing.

Version 2.3.0 of the CLI introduces a change on distributed trace log messages and fixes two bugs on the frontastic upload command.

Distributed trace log messages in the extension log window are now hidden by default, you can display them by changing the settings in the filter dialog, which opens by pressing F. This improves the visibility of extension log messages in the CLI because the distributed trace messages prevented their display.

Additionally, we fixed two bugs on the frontastic upload command:

• The CLI no longer requests the frontastic.toml configuration file because the command already receives the configuration parameters. Previously, the CLI requested the file anyway.
• Errors no longer occur when running the CLI as a root user.

Additional components are now available in the B2B store template:

• Search listing page
• Product details page
• Checkout page

With these additions, the B2B template provides users with enhanced functionality to create a more seamless shopping experience.

You can now use a Git hosting service of your choice for the repository of your commercetools Frontend project. This gives you more flexibility in choosing your preferred Git hosting service and using a custom continuous integration.

Following this change, the scaffold and upload CLI commands are now available to help set up your custom repository.

The Studio underwent some modifications to support this new feature change.

Version 2.1.1 of the CLI is now available and it fixes two bugs on logs.
Large log messages did not appear in the CLI, which prevented any subsequent logs from being displayed as well. Now, logs appear as expected.
Additionally, multiple empty log messages were displayed after starting the CLI. Now, they no longer appear.

We've integrated commercetools Checkout, our end-to-end checkout solution, into the B2C store template. With this enhancement, the B2C store template now provides a seamless and efficient checkout solution out of the box.

A ready-made B2B store template is now available in the commercetools Frontend customer project. You can use the template to create a B2B commerce website and leverage the functionalities of both commercetools Frontend and commercetools Composable Commerce.

A ready-made B2C store template is now available in the commercetools Frontend customer project. You can use the template to easily create a B2C commerce website and leverage the functionalities of both commercetools Frontend and commercetools Composable Commerce.

You can now preview and test the frontend and backend code of your website together, using automatic branch deployments. When you create a pull request, commercetools Frontend CI builds and deploys your backend, while Netlify deploys your frontend website.

Your Netlify administrator must configure Deploy Previews on Netlify.

The out-of-the-box Bloomreach extension reduces development effort to integrate Bloomreach with your commercetools Frontend project.

With the extension, you can deliver Bloomreach content to your commercetools Frontend website.

The out-of-the-box Talon.One extension reduces development effort to integrate Talon.One with your commercetools Frontend project.

With the extension, you can use discounts, coupon codes, and other promotional marketing features from your Talon.One campaigns.

The out-of-the-box Nosto extension reduces development effort to integrate Nosto with your commercetools Frontend project.

With the extension, you can deliver product recommendations from Nosto to your commercetools Frontend website.

commercetools Frontend now has a multi-tenant backend architecture. This change lets you serve your API hub instance for your commercetools Frontend projects in a more scalable and efficient way.

The main improvements resulting from this new architecture are:

• You will no longer use sandboxes to develop extensions. An environment in a development cluster is created automatically.
• Website latency will decrease since cloud functions run on a cluster close to your customer’s target location.

If your projects are already set up on the new multi-tenant architecture, you do not need to take any actions.

If your projects are set up on the old single-tenant architecture, you need to perform some changes. Please contact your Customer Success Manager for further information.

The Studio underwent some modifications to support this change.

Our documentation is updated to reflect the changes.

As of today, you can monitor the commercetools Frontend system status and metrics from the general commercetools system status page. This will allow you check the status of commercetools Frontend and Composable Commerce at a glance from the same place, instead of from two different pages.

From the commercetools system status page, you can also subscribe to be notified of status updates.

The old commercetools Frontend system status page will no longer be available.

The out-of-the-box Dynamic Yield extension reduces development effort to integrate Dynamic Yield with your commercetools Frontend project.

With the extension, you can deliver product recommendations from Dynamic Yield to your commercetools Frontend website.

The out-of-the-box Contentstack extension reduces development effort to integrate Contentstack with your commercetools Frontend project.

With the extension, you can deliver Contentstack media content (such as images, videos, and other media assets) to your commercetools Frontend website.

The out-of-the-box Amplience extension reduces development effort to integrate Amplience with your commercetools Frontend project.

With the extension, you can deliver Amplience media content (such as images, videos, and other media assets) to your commercetools Frontend website.

The Good Store is a frontend template to launch a storefront in a short time. The Good Store frontend components were designed according to research on commerce UX/UI best practices.

You can use The Good Store as a blueprint to build and launch your commerce website with commercetools Frontend and commercetools Composable Commerce, or you can just take it as a reference to develop your commerce website.

The Good Store is built using commercetools Frontend SDK and comes with the following integrations:

• Adyen
• Algolia
• Google Tag Manager
• SendGrid

Version 2.0.0 of the CLI fixes a bug on Windows systems where linking dependencies would fail if the commercetools Frontend project is on a different drive than the CLI binary.

commercetools Frontend SDK was introduced to help create integrations with commercetools Frontend.

The SDK improves the experience of developers with utilities and developing new integrations because it allows working autonomously, with minimal support needed.

The commercetools Frontend SDK comes with the following NPM packages:

• @commercetools/frontend-sdk
• @commercetools/frontend-composable-commerce
• @commercetools/frontend-domain-types

Version 1.25.0 of the CLI introduces a feature and fixes a bug.

New feature

You can now see the URL to the Studio from the dashboard and you can open it by pressing S.

Bug fix

Copying log entries to the clipboard by pressing c crashed Linux systems, the bug was fixed.

As you already know, commercetools acquired Frontastic in November 2021. As a step towards the post merger integration, we've rebranded the Frontastic Next.js offering as commercetools Frontend.

The release notes published before 4 November 2022 are archived below.