Document Tree
Document Properties
Last Modified
Added to KB
Public Access
Doc Type
Intershop Progressive Web App
Guide - Intershop Progressive Web App - Migrations

From 5.1 to 5.2

The store action and method addBasketToNewOrderTemplate of the OrderTemplatesFacade have been renamed to createOrderTemplateFromLineItems and refactored slightly.

The Intershop PWA specific Pipes sanitize, makeHref and htmlEncode were renamed using the common ish prefix that is used for the other custom Pipes as well.
When migrating all occurrences of these Pipes need to be renamed to ishSanitize, ishMakeHref and ishHtmlEncode.
The code generation was adapted to generate new Pipes from the beginning with the correct prefixes now.

A few Stylelint rules were changed and the .scss files were adapted.
color-function-notation was changed to the default modern resulting in changed color notations from rgba(0, 0, 0, 0.125) to rgb(0 0 0 / 0.125)
scss/no-global-function-names was enabled resulting in changes e.g. from map-get($grid-breakpoints, 'xs') to map.get($grid-breakpoints, 'xs') with the necessary @use references or from darken($color-label-new, 20%) to color.adjust($color-label-new, $lightness: -20%).
In addition empty comments in .scss files are no longer allowed and removed.
In migration projects either keep the Stylelint rules with the old settings or migrate all your styling files accordingly running npm run format.

The method encodeResourceID is now used to encode all dynamic resource IDs in any REST API call.
This was previously only done for the login but is now consistently used for all resource IDs.
For ICM 7.10 and ICM 11 this is done by default with a duplicated encodeURIComponent encoding.
For ICM 12 and newer this needs to be changed to a single encodeURIComponent with additional + character handling.
The ICM 12 handling is already prepared in encodeResourceID and needs to be activated in the source code if the Intershop PWA is used together with ICM 12.

With the Intershop PWA version 5.2.0 the rendering of our demo/example view contexts was disabled by default.
Each integrated view context triggers a REST call that will potentially decrease the SSR rendering performance, something that is not necessary if this feature is not actively used in a PWA project.
For that reason the examples were commented out in the source code and have to be activated in the project source code if needed.
See CMS Integration - View Contexts for more information.

The ExternalDisplayPropertiesProvider setup notation was changed from providing only the product context to providing a combined { product, prices } context object.
For that reason any custom ContextDisplayPropertiesService that implements the ExternalDisplayPropertiesProvider needs to be adapted accordingly (see the changes of #1657).

The dead code detection script was improved and extended and is now checking Angular components in more detail.
This resulted in more variables and methods being declared as private and some unused code being removed.
This should not affect PWA based projects as long as such internal declarations were not used, else compiling will fail and the code would need to be adapted/reverted accordingly.

Product variations were eagerly loaded via effects.
In projects with a lot of Variations, this can lead to performance issues, especially if the variations data is not needed for the current views.
For that reason product variations are now loaded lazily through the following changes that might need adaptions with project customizations.

  • The variations property on the product view interface was removed. Variations can now be retrieved via the product context facade or the shopping facade.
  • The productMaster property on the product view model has been removed. The master product should be individually retrieved.
  • The ish-product-item-variations component has been refactored.

The Formly wrapper textarea-description was renamed to the better suited name maxlength-description and the rendering logic and compatibility to the general description wrapper was improved.
The renaming should better convey the fact that this wrapper can be used not only for ish-textarea-field (where it is configured by default) but with other input field types as well.
Besides this the main difference to the general description wrapper is its remaining maxlength calculation.
Together with the renaming the implementation was changed so that the description will only be rendered if the according field has a props.maxLength value configured.
And the props key to provide an alternative translation key was changed from customDescription to maxLengthDescription.
This change provides the possibility to use the description wrapper with its customDescription together with the maxlength-description wrapper with a customized maxLengthDescription.
For the migration of customer projects it needs to be checked whether a customDescription is configured for a ish-textarea-field and if so it needs to be replaced with maxLengthDescription.
Additionally it needs to be checked if the textarea-description wrapper is configured anywhere else then the default assignment to the ish-textarea-field.
If so these wrapper configurations need to be replaced with maxlength-description.

From 5.0 to 5.1

The OrderListComponent is strictly presentational, components using it have to supply the data.
The getOrders method of the OrderService does not fetch all related order data by default, you can provide an additional parameter to include the data you need.

For accessibility reasons, we use buttons instead of anchor tags for links that only trigger an action and are not intended for navigation purposes.
Note the following minor styling changes: use CSS classes btn btn-link btn-link-action for text links and btn-tool btn-link for icon links, (see Accessibility guide/How to fix 'click-events-have-key-events' problems for more details).

In ICM 11 the messageToMerchant flag can be configured in the back office and its setting is supplied by the /configurations REST call.
For this reason, the messageToMerchant feature toggle has been removed as a configurable feature toggle.
To still be able to configure the message to merchant feature via feature toggle in ICM 7.10 environments, an ICMCompatibilityInterceptor has been introduced that can be enabled in ICM 7.10 based projects in the core.module.ts.
In addition, the 'messageToMerchant' environment feature toggle option needs to be enabled in the environment.model.ts.

To address an Angular hydration issue (#1585), the header component rendering has been changed and, in addition, a HeaderType has been introduced for the standard header types ['simple', 'error', 'checkout'].
If other header types are used in a project, these header types and the rendering need to be adapted accordingly.

With the introduction of the new navigation CMS components it became necessary to adapt the main navigation styling.
The styling can no longer rely on child selectors (>), since the CMS managed components introduce a lot of additional HTML tags around the styling-relevant li tags.

To improve the performance of the 'Static Content Page' component, the default behavior of the triggered /pagetree REST call regarding the used depth has been changed.
Previously, no 'Navigation Depth' specified in the Commerce Management configuration resulted in no limitation at all ("Define how many levels the navigation tree displays.
To show all levels, leave the field empty.").
With the content model adaptions of icm-as-customization-headless:1.7.0, a depth default value of 5 has been introduced and the description has been changed accordingly.
In the PWA, the rendering was adapted as well so that an empty NavigationDepth value of the 'Static Content Page' component now defaults to 0 instead of no depth limitation that resulted in the whole content page tree being fetched and saved to the state.
To keep the current behavior in an existing project, either adapt the 0 default in pagelet.numberParam('NavigationDepth', 0)" to a reasonable number or set the 'Navigation Depth' values for all 'Static Content Page' component instances in Intershop Commerce Management to reasonable depth values instead of leaving them empty.

The Brotli NGINX module is used instead of gzip for compression on the NGINX server now, see NGINX Optimizations.

The rendering of the CMSImageEnhancedComponent has been changed and is no longer loading the image with loading="lazy" by default.
See the Enhanced Image Teaser section in "Guide - Core Web Vitals" for further information.

From 4.2 to 5.0

Starting with the Intershop PWA 5.0 we develop and test against an Intershop Commerce Management 11 server.
For this reason the official Intershop Commerce Management requirement is now ICM 11 even though the PWA 5.0 will continue to work with current ICM 7.10 versions as well.
In the changelog of this project we will inform about features that will only work with ICM 11 or ICM versions above 7.10.38.x-LTS releases.
With the transition to ICM 11 the configured default icmBaseURL is now ''.

With the switch to ICM 11 we switched to ICM deployments without the Responsive Starter Store as well.
Because of this, the default icmApplication is now configured to '-'.
For ICM deployments with the Responsive Starter Store this probably has to be configured as it was before with 'rest'.

The project has been updated to work with Angular 16.
Besides this, a lot of other dependencies (NgRx, Typescript) have also been updated.

The spelling of the OCI punchout actions has changed due to a changed naming schema of the NgRx action creator functions.

Since defaultProject is no longer a valid option in angular.json, it has been removed and the root project (project with an empty root) is used instead.

We enabled the Angular Hydration to improve performance and prevent the UI from flickering when a page renders - please note that this feature is still in developer preview and may have some limitations.

From this version, we use the takeUntilDestroyed operator to complete observables when the calling context (component, directive, service, etc) is destroyed.
The add-destroy schematic has been removed but you can keep the takeUntil(destroy$) mechanism for a transitional period.
A migration script is created to support the migration to the new way to complete open observable subscriptions on destroy.
This script can be executed with npx ts-node .\scripts\migrate-destroy-subject.ts.
Please review all changes after running the script and make sure all files work as expected.
Also, any unused imports within the files must be removed (npm run lint --fix can be used).

We added the ESLint rule @angular-eslint/template/prefer-self-closing-tags to use self-closing tags in HTML files (npm run lint --fix can be used to update your HTML files).

The ngcc command has been removed from the package.json because it is no longer supported or needed in Angular 16.

Mandatory component input parameters are declared as required to ensure that all required data is provided.
This enforces data dependencies and catches potential errors during compilation.

For the optional use of a shared Redis cache we switched from the plain standard NGINX Docker image to an OpenResty Docker image, which provides more flexibility in configuring the underlying NGINX.
If the NGINX container has been customized in the project, you need to check that these customizations work with the OpenResty image in the same way.
Without any customizations, the switch should be unnoticeable and does not require any adaptions.

The input parameter id for the product listing component is now called productListingId to avoid unintentionally having more than one element with the same ID in the HTML document.
The api-token.service has been refactored and the class variables apiToken$ and cookieVanishes$ have the private modifier.
Use the public getter/setter methods to access these variables outside the class.

Basket line-item functionalities have been extracted from the basket.service into a separate basket-items.service.
The action UpdateBasketLineItems as well as the LineItemUpdateHelper have been removed because they were unused for a long time.

From 4.1 to 4.2

The basket attribute orderReferenceId is now saved as native attribute externalOrderReference at the basket, but it still exists at the basket and can still be displayed if required.

A better handling of cookie SameSite and secure settings was implemented with new defaults to SameSite=Strict and secure.
This can still be overridden by calling the put method with explicitly set values.
The secure setting is now always set to true when in https mode.
You can prevent this by explicitly setting it to false.
If the PWA is run in http (which should only be in development environments), secure is not set.
Additionally, if the PWA is run in an iframe, all cookies are set with SameSite=None (e.g., for Punchout or Design View).
Be aware that some browsers will not accept cookies with SameSite=None without secure.
Previously, no SameSite was set by default, so browsers treated it as SameSite=Lax.
This needs to be set explicitly now if it is really intended.
To migrate, check if the cookies.service put method calls need to be adjusted.

The user's language selection is now saved as a cookie (preferredLocale) and restored after the PWA has loaded.
This functionality can be enabled or disabled with the feature toggle saveLanguageSelection.

From 4.0 to 4.1

The Intershop PWA now uses Node.js 18.16.0 LTS with the corresponding npm version 9.5.1 to resolve an issue with Azure Docker deployments (see #1416).

As a leftover adaption regarding the switch from deprecated class-based route guards in favor of functional guards, the addGlobalGuard function was adapted to work with functional guards.
If the addGlobalGuard function is used for customizations, make sure it now works as expected.

The input parameter id of the component ish-product-quantity caused issues with duplicate IDs within the page's html.
Therefore, it was renamed to elementId.
If the input parameter id of this component has already been used, it has to be renamed accordingly.

The ishIntersectionObserver returns all three IntersectionStatus change events: Visible, Pending, and NotVisible as well now.
The custom project code needs to be adapted if it does not filter the events where it is used (e.g., if (event === 'Visible')).

The two standard themes b2b and b2c where refactored in such a way that the b2c theme could be changed into a configurable theme that uses CSS custom properties (CSS variables).
Since SCSS color calculations do not work with CSS custom properties (they need real values instead of var(--corporate-primary)), SCSS functions like darken() and lighten() were removed from the standard Intershop PWA SCSS styling.
Existing projects that do not want to use a configurable theme do not need to apply these changes to their custom styling.

To use the new configurable theme feature, the feature toggle extraConfiguration needs to be enabled.

A new TokenService is introduced, which is only responsible for fetching token data from the ICM.
However, all necessary adaptions for the identity providers and the fetchToken() method of the UserService are removed in order to be completely independent of TokenService.
If your identity providers should use the OAuthService to handle the authentication, please make sure to instantiate a new OAuthService entity within the identity provider.
The getOAuthServiceInstance() static method from the InstanceCreators class can be used for that.
Furthermore, the handling of the anonymous user token has been changed.
It will only be fetched when an anonymous user intends to create a basket.

We added an Address Doctor integration as a new extension which can be enabled with the feature toggle addressDoctor and additional configuration.

From 3.3 to 4.0

The Intershop PWA now uses Node.js 18.15.0 LTS with the corresponding npm version 9.5.0 and the "lockfileVersion": 3,.
For migrating the package-lock.json, it is always advised to use the package-lock.json from the Intershop PWA and then run npm install to update it with the additional custom dependencies from the customer project's package.json.

The project was updated to work with Angular 15.
This includes the removal of the Browserslist configuration and an updated TypeScript compiler target and lib to ES2022 (for browser support requirements that differ from the Angular 15 standard configuration, see the configuring browser compatibility guide and the TypeScript configuration reference).
Adaptions of the Schematics configurations and tests were also necessary.
In addition, all other dependencies were updated as well and resulted in necessary Stylelint and Jest test adaptions.

The placeholder for theme-specific assets and styles has been changed from placeholder to theme_placeholder.
If this is used in any customization, update all paths which are using the old theme placeholder, e.g., src/styles/themes/placeholder to src/styles/themes/theme_placeholder.

The injection token LOCAL_TRANSLATIONS was introduced to use local translation files within the custom ICM translation loader.
A factory function is provided in the internationalization.module.ts to decide which json file with translation keys should be used for a given language.

  providers: [
      provide: LOCAL_TRANSLATIONS,
      useValue: {
        useFactory: (lang: string) => {
          switch (lang) {
            case 'en_US':
              return import('../../assets/i18n/en_US.json');
            case 'fr_FR':
              return import('../../assets/i18n/fr_FR.json');
            case 'de_DE':
              return import('../../assets/i18n/de_DE.json');

Please adapt the useFactory() function to return all imported local translation files depending on the lang parameter.

With Angular 15 class-based route guards are deprecated in favor of functional guards.
Thus, we removed the guard classes and replaced them by functions.
For the canActivate/canChildActivate methods, only change the class name into the function name by lowercasing the first letter, e.g.,

  path: 'organization-management',
  canActivate: [AuthGuard],
  canActivateChild: [AuthGuard],

will become

  path: 'organization-management',
  canActivate: [authGuard],
  canActivateChild: [authGuard],

For more information about functional guards, see this blog article.

With the Prettier update to version 2.8 the format of pipes in HTML files changed slightly.

After updating Jest to version 29 the default snapshot formatting changed.
Run npm run test -- -u to update your test snapshots.

The account navigation has been reworked to support navigation grouping (used in b2b theme, see account-navigation.items.ts).
For better maintainability and brand-specific overriding, the account navigation items were externalized in an extra file account-navigation.items.ts used by the account-navigation.component.ts.
With this rework also the navigation items data structure was changed from a key value object to a simpler NavigationItem array.
With this data structure accessing the data was changed for the key access from item.key to item.routerLink, or for the value example from item.value.localizationKey to item.localizationKey.
To migrate to this new account navigation item handling, any account navigation customization needs to be adapted accordingly.

The deprecated SSR environment variable ICM_IDENTITY_PROVIDER was completely removed.
Use the variable IDENTITY_PROVIDER instead to select the identity provider to be used if it is not the default ICM.
We removed the default identityProvider configuration from environment.model.ts, so only the hardcoded fallback from configuration.effects.ts works as fallback.

The deprecated properties templateOptions and expressionProperties have been removed from the FormlyFieldConfiguration object.
Current projects must use the new properties for all formly field configurations.
You must adapt html templates, too, when using the deprecated properties in there.

To replace deprecated formly field properties, you can execute the new formly-migrate schematic.
Please run the following command for each configured Angular project (e.g., 'intershop-pwa'):

  ng g formly-migrate --project=${ANGULAR_PROJECT}


Not all scenarios where a deprecated property could be found are taken into consideration for the formly-migrate schematic. Please check and adapt your code manually for additional changes. For further information, see the formly migration guide.

The templates of account-order-template-detail-page.component.ts, quote-line-item-list.component.ts, quoting-basket-line-items.component.ts, and account-wishlist-detail-page.component.ts have been updated to ensure correct DOM element updates for ngFor loop changes.
A trackBy function will be used now.

Obsolete functionality that is no longer needed with the current state of the Intershop PWA was removed from the project source code:

  • Removed outdated kubernetes-deployment schematic that could be used to create Kubernetes charts. Use the official Intershop PWA Helm Chart repository instead.
  • Removed unused azure-pipeline schematic that could be used to create an Azure Pipeline template based on the generated Kubernetes charts for DevOps.
  • Removed migration scripts that were used for pre PWA 1.0 migration support.
  • Removed obsolete TODO comments and related logic that handled, for example, wrong/odd/old REST API quirks.

We recommend to use the Action Group Creator to create store actions now.
Therefore, the corresponding store schematic for the action creation has been adapted.

We added some helper methods to improve the use of dependency injection.
Use the method createEnvironmentInjectionToken now to define new injection keys for environment variables in the injection-keys.ts.
If you want to inject a token, use the methods injectSingle and injectMultiple to secure the type safety of your injected variables (except for Angular core tokens, which are forced to a type).
There is a new linting rule useTypeSafeInjectionTokenRule that enforces the usage of these methods.
For more information, see the Configuration Concept.

We introduced the product notifications feature as a new extension which can be enabled with the feature toggle productNotifications.

From 3.2 to 3.3

To improve the accessibility of the PWA in regards to more elements being tab focusable, a lot of [routerLink]="[]" where added to links that previously did not have a link reference.
Also some (keydown.enter) event bindings with tabindex="0" were added to ensure a better interactivity with the keyboard only.
If the according commits lead to problems, they could be skipped and resolved later by fixing the accessibility linting issues manually.
More information regarding accessibility in the PWA and the used ESLint rules can be found in the Accessibility Guide.

From 3.1 to 3.2

A styling adaption was made to the application shell to expand it to the full page height, so the footer now always stays at the bottom.
Together with that an inline style of the main-container was moved to the global styling definition.

Formly has been upgraded from version 5 to 6.
For more information, see the Formly Upgrade Guide.
We still use deprecated form properties like templateOptions and expressionProperties for compatibility reasons but we are going to replace them in the next major release.

The two small black triangle images active_catalog.png (header: when hovering a catalog) and budget-bar-indicator.png (my account: budget bar) are removed and replaced by CSS styling.
The image for an empty basket empty-cart.png is removed and replaced with CSS styling.
The sprite image product_sprite.png is removed and replaced with localized text for "New", "Sale", and "Top" with the according CSS styling.

After entering a desired delivery date on the checkout shipping page and after submitting the order, the desired delivery date will be saved at all basket items if necessary.
In case of large baskets (> 20 items) this might cause long response times.
You can keep the existing behavior by modifying the updateBasketItemsDesiredDeliveryDate() method of the basket service to always return an empty array without doing anything.

The ProductsService was changed to use extended=true REST calls for product details and variations to fetch variation attributes with additional attributeType and metaData information that can be used to control the rendering of different variation select types.
The added VariationAttributeMapper maps the additional information in a backwards compatible way.
To handle the different variation select rendering types, the existing ProductVariationSelectComponent now contains the logic to select the fitting variation select rendering component.
The rendering and behavior of the existing ProductVariationSelectComponent as a standard select box was moved to the new ProductVariationSelectDefaultComponent.
A ProductVariationSelectSwatchComponent for colorCode and swatchImage variation select rendering and a ProductVariationSelectEnhancedComponent for a select box rendering with color codes or swatch images and a mobile optimization were added.

The user authentication process has changed.
User authentication tokens are requested from the ICM server using the /token REST endpoint now.
Regarding this, the logout action triggers a service which revokes the currently available access token on the ICM back office.
If the logout was successful, all personalized information is removed from the ngrx store.
Please use logoutUser({ revokeToken: false }) from the account facade or dispatch logoutUserSuccess instead of the logoutUser action to use the old behavior.

From 3.0 to 3.1

The SSR environment variable ICM_IDENTITY_PROVIDER will be removed in the next major release (PWA 4.0).
Use variable IDENTITY_PROVIDER to select the provider to be used instead.
Keep this in mind before deploying or starting the Intershop PWA in server-side rendering mode.

The default value of the input parameter 'queryParamsHandling' has been changed from 'merge' to '' for the components product-name.component and product-image.component.
This has been done to prevent an unintentional application of filters for product variation master links if the product detail link does not originate from a product listing context (product list page, search result page).

To prevent deprecation warnings, we removed the unnecessary ~ from all 3rd party SCSS imports (see - "Using ~ is deprecated and can be removed from your code (we recommend it)").
This should be done for additional imports in the customizations as well.

The validator equalToControl did not work properly.
For that reason we removed it.
Use the validator equalTo instead.
For more information, see the method description in the special-validators.ts.

The "Product Image Not Available" PNG image not_available.png is removed and replaced by an SVG image not-available.svg which does not include a text inside the image anymore to avoid localization issues.
The file references are updated accordingly, the product image component is updated to use the correct image attributes, a localized alternative text is added, and the product and image mapper files are updated to provide the correct data.
In case the current PNG image file and the handling is customized in a project, you have to ensure to keep the project changes.

From 2.4 to 3.0

With the 2.4.1 Hotfix we introduced a more fixed Node.js version handling to the version used and tested by us.
We set Node.js 16.16.0 and npm 8.11.0 as our application runtime and package management versions.
This is supposed to prevent unexpected build issues in the future but requires manual updating of Node.js to newer versions if tested successfully.
Other Node.js versions might still work but you might get warnings regarding the project's recommended settings.

The Intershop PWA 3.0 release includes a Jest Update to version 28, see also
The jest-marbles package has been replaced by jasmine-marbles.

It also contains the Angular 14 update and updates to a lot of other dependencies (NgRx, Typescript).
These updates require some code adaptions, e.g., form classes have been prefixed with Untyped wherever necessary.
The following official guides might help to migrate custom code as well:

Because Angular 14 now uses yargs to parse CLI arguments (see #22778), schematic options with a no prefix are handled differently.
With #23405, the Angular team has introduced a temporary workaround for this.
In order to reliably maintain compatibility in the future, the cms schematic's noCMSPrefixing option has been renamed to cmsPrefixing with an inverted behavior.

Cypress has been upgraded from version 9 to 10.
We went through the interactive migration to move our spec files from cypress/integration folder to the cypress/e2e folder and updated the config file as well as some scripts.
For more information, see the Cypress Migration Guide.

Since the used deferred load library is no longer maintained, it is removed and has been replaced with similar standard browser functionality loading="lazy".
All uses of the (deferLoad) directive in custom code need to be replaced.

We removed the unmaintained angular2-uuid library in favor of the standard uuid library that is already included as an Angular dependency.
In order to match our changes, replace all occurrences of angular2-uuid in your custom code (see #1203).

The pagespeed module of NGINX has been removed without replacement.

The @ngx-translate/http-loader dependency was removed since we did not use it.
You might need to keep this dependency if you are loading translations differently from the standard Intershop PWA in your customization.

The deprecated customized-copy schematic for copying components and replacing all usages was removed.

We introduced a build variable SSR that is now used for all checks if the application is running in SSR or browser context.
We no longer use the verbose way of injecting the PLATFORM_ID and check it with the methods isPlatformBrowser or isPlatformServer.
This way still works but it is discouraged by a new ESLint rule that suggests using the new SSR variable instead.
So running npm run lint will help finding custom code that still relies on the platform checks.

To support, e.g., special characters in e-mail addresses with newer versions of ICM (7.10.38.x), like +, double encoding of resource IDs in the REST API calls is necessary.
With the method encodeResourceID we provide a central place that implements the fitting resource encoding.
In the PWA this was applied to all user logins in REST API calls.
For project customizations, the usage of the native encodeURIComponent functionality should be replaced with encodeResourceID for user logins in REST calls as well.

The footer.content localization key was replaced for most of its content by a CMS manageable content include include.footer.content.pagelet2-Include that is available from ICM

For better Search Engine Optimization the route formate and route handling for products, categories, and content pages has been reworked.
All these routes now contain hierarchies and have different ID markers.
For categories it was changed from cat to ctg and for products from skuto prd.
This way, it is intended to have less conflicts and limitations with potential category/product IDs, e.g., 'cats' or 'skunks'.

To improve the support of large baskets we update the ngrx store immediately after adding, updating, and deleting basket items now.
Therefore, we had to change the return values of the corresponding basket service functions as well as the payload of the success actions.
We also limited the number of displayed line items in the mini basket and introduced a paging bar on the basket page to speed up the rendering of these components.

From 2.3 to 2.4

The PWA 2.4 contains an Angular update to version 13.3.10 and many other dependencies updates.
These updates did not require any updates to the PWA source code.
But it needs to be checked if this is true for your project customizations as well.

We introduced a checkout guard that protects the checkout routes in case no shopping cart is available and navigates back to the empty basket page.

Routes to non-existing CMS content pages now result in a "Page Not Found" error page.

The 'ratings' functionality (components concerning the display of product ratings) has been moved into an extension using the existing feature toggle 'ratings'.

With the display of product reviews the attribute 'numberOfReviews' has been added to the product model, and the number of reviews is displayed behind the product rating stars now instead of the average rating that is already depicted in the stars.

From 2.2 to 2.3

The 'contact us' functionality has been moved into an extension and we have introduced the feature toggle contactUs in the environment.model.ts that is switched on by default.

The getFilteredProducts method has been moved from the FilterService to the ProductsService, since the /products API is used.
Together with this change, the default product attributes for product listings have been externalized and are easily overridable now.

With #1135, the default model representation used by NgbDatepicker is the native ES6 Date now.
During this refactoring, the DateHelper class has been removed. This will not concern you if you use ish-date-picker-field directly.
However, if you use NgbDatepicker outside of formly, some helpers you might have used are gone.
Please use the underlying functions from Date, NgbCalendar and date-fns directly, or create your own DateHelper.

From 2.1 to 2.2

The PWA 2.2 contains an Angular update to version 13.3.0 and many other dependencies updates.

These updates required some internal webpack handling changes especially for the template overloading.

Also, some test adaptions where necessary, so is it now necessary to mock the SwiperComponent.

Another change is the Formly downgrade from v6 pre-release to v5 that still works with Angular 13 with a changed ngcc setting.

After the updates, the deprecated RxJS MapTo operators (mapTo, mergeMapTo, switchMapTo) were replaced Deprecating MapTo variants.
Linting will point out these issues in custom code that can easily be replaced then.

The Intershop PWA now uses Node.js 16 LTS with a corresponding npm version >=8.0.0.
With this new npm, calls using npx npm-run-all in CI have to be changed to npm run exec npm-run-all.

Changes with Angular 13 require to declare less dependencies in test beds than before.
For that reason the PWA 2.2 contains two pull requests that cleanup a lot of test specs (see #1057 and #1072).
It is not considered a breaking change but it might result in merge conflicts with customized Jest tests.
To cleanup the own code base run npm run cleanup-testbed.
Run npm run cleanup-testbed -- --help for more detailed options.

The shared/formly folder - containing all custom types, wrappers, etc - was updated.

For a cleaner separation of code artifacts, there are now multiple subfolders declaring their own modules where formly is partly configured.
The FormlyModule brings all these together, so you can use it just like before.
If you made any changes in shared/formly, you will have to adapt the corresponding modules.

Additionally, we introduced a formly/field-library subfolder that contains a FieldLibrary service which enables you to define reusable FormlyFieldConfigs and access them easily.
If you have customized anything in shared/formly-address-forms/configurations/address-form-configuration.ts, for example, the standardFields variable, you will have to migrate these changes by defining new FieldLibraryConfigurations.
The address form configurations now use the new FieldLibrary functionality under the hood.

For more information, read the new Field Library documentation.

The compare products functionality was moved into an extension.
The already existing compare feature toggle works as before but the compare components integration changed to lazy components, e.g., <ish-product-add-to-compare displayType="icon"></ish-product-add-to-compare> to <ish-lazy-product-add-to-compare displayType="icon"></ish-lazy-product-add-to-compare>.
For other compare components, check the compare-exports.module.ts file.

From 2.0 to 2.1

The recently viewed products functionality was moved into an extension.
The already existing recently feature toggle works as before but the recently viewed component integration changed from <ish-recently-viewed *ishFeature="'recently'"></ish-recently-viewed> to <ish-lazy-recently-viewed></ish-lazy-recently-viewed>.
This has already been changed for the product detail page and the basket page but needs to be done for any customized usage of the recently viewed component.

The clean-localizations functionality was changed so that keep-localization-pattern can be defined where they are used and do no longer need to be added directly to the clean-up-localizations script.
It might be useful to move custom patterns according to the changes done for the standard code (for more information see Localization File Clean Up Process).

TestBed configuration arrays are sorted again as of 2.1 This means a lot of (small, auto-fixable) changes across the codebase.
Simply run ng lint --fix in order to sort your arrays.
If you have a lot of migration changes, you might be required to run it more than once.

With the introduction of personalized REST calls for categories and products, data in the ngrx store runs the risk of not being up-to-date after a login or logout.
To fix this, a new resetSubStatesOnActionsMeta meta-reducer was introduced to remove potentially invalid data from the store.
If the removal of previous data from the store is not wanted, this meta reducer should not be used in customized projects.
In addition, a mechanism was introduced to trigger such personalized REST calls after loading the PGID if necessary.
This way of loading personalized data might need to be added to any custom implementations that potentially fetch personalized data.
To get an idea of the necessary mechanism, search for the usage of useCombinedObservableOnAction and personalizationStatusDetermined in the source code.

From 1.4 to 2.0

Since TSLint has been deprecated for a while now, and Angular removed the TSLint support, we had to migrate our project from TSLint to ESLint as well.
This means in version 2.0 all TSLint rules and configurations were removed and replaced by ESLint where possible.

This not only required configuration changes in the Intershop PWA project but also application code adaptions to comply with some of the new ESLint rules.
To allow for an as easy as possible migration of existing PWA projects, we split the whole switch in separate commits that should make it easier to resolve potential merge conflicts by providing some context, e.g., changes to satisfy a specific rule or project configuration changes etc.
We advise you to first cherry pick all the eslint commits provided by the PWA release before applying the lint rules to the project customizations to fix the issues that reside in the project code.
If the found issues are too many to address them in an ordered manner, it is probably best to temporarily disable some of the failing rules in .eslintrc.json (see Configuring ESLint and to only fix one after another.

It is also probably a good idea to do the PWA 2.0 migration not in one go as described in Import Changes from New PWA Release but to first do the commits before the linter switch and bring your project to a clean state (npm run check).
After this, all the linter switch commits should be applied and the project should be brought back to a clean state.
Once this is done, subsequent commits should be migrated.
If your project contains own custom TSLint rules, you will have to re-implement them as ESLint rules to be able to apply them to your code base (see Custom ESLint rules).

With version 2.0 we introduce a renaming of the two standard PWA themes and change the default theme:

  • The previous B2B theme blue is now called b2b and is used as default theme from now on.
  • The previous B2C theme default is now called b2c.

With this change the according folders and references had to be renamed/moved and need to be adapted in customer projects as well.
In projects where the recommended procedure for using a custom theme has been followed (see Customization Guide - Start Customization), minimal migration effort should be required.

We moved the model SelectOption from the select.component.ts to the select-option.model.ts and adapted all necessary imports.

In the PWA 0.28 we introduced the usage of Formly to generate and maintain our forms.
Now we removed the obsolete form components.
If you want to use the obsolete form components in your project nevertheless, skip the commit remove obsolete form components.
For more information concerning Formly please refer to our Formly - Guide).

The feature toggle 'advancedVariationHandling' has been removed.
Instead the ICM channel preference 'AdvancedVariationHandling' is used to configure it.
You will find this preference as 'List View' in the ICM backoffice under Channel Preferences -> Product Variations.

The ICM channel preference 'basket.maxItemQuantity' is included to validate the product quantity if no specific setting is defined on the product.
You find this preference as 'Maximum Quantity per Product in Cart' under the Application Settings -> Shopping Cart & Checkout.
The default value is 100.

The Intershop PWA 2.0 release includes the Angular 13 update and updates to a lot of other dependencies (NgRx, RxJS, Formly, Swiper).
These dependencies updates require many necessary code adaptions that are included in additional commits.
The following official guides might help to migrate custom code as well:

To help with the necessary rxjs refactorings, consider using rxjs-fixers-morph.
Simply run npx rxjs-fixers-morph ./tsconfig.json.

From 1.1 to 1.2

The dist folder now only contains results of the build process (except for healthcheck.js).
You must not edit any file inside that dist folder, since this would include not being able to change Kubernetes liveness or readiness probes we included SSR container related source code under src/ssr/server-scripts/

From 0.31 to 1.0

The Angular configuration mechanism of the Intershop PWA was refactored to support running multiple configurations in one Docker image (see Guide - Multiple Themes).
This now means that the former environment.local.ts which had a standalone configuration can no longer be supported.
Instead, theme-specific environments exist for default and blue, and development settings can be overridden in environment.development.ts, which are imported into the theme-specific configurations (see Guide - Development).
npm install will create an initial version of the environment.development.ts that can be filled with the needed information from environment.local.ts.
The environment.local.ts itself becomes obsolete and can be deleted.

Locale definitions in environment.ts models are no longer supported, only ICM channel configurations are now used for switching locales.

From 0.29 to 0.30

We introduced the feature toggle 'guestCheckout' in the environment.model.ts.

We switched to encode user logins when used in the api service.
This is to enable special characters (like the #) that are sometimes present in user logins (SSO case!) but would have led to errors before.

From 0.28 to 0.29

We activated TypeScript's noImplicitAny.
Please refer to the Type Safety part in the Getting Started Guide for motivations.

From 0.27 to 0.28

We removed the property production from Angular CLI environment.ts files.
Production mode can consistently be set by using Angular CLI configurations now.
This also works when running multiple configurations like --configuration=brand,production.

We removed the property serviceWorker from Angular CLI environment.ts files.
The Service Worker can now be set consistently depending on the current configuration in the angular.json file.

We removed the dependency to ngx-swiper-wrapper as it will no longer be supported and swiper itself now natively supports Angular (see changes #552).

We introduced formly to handle all kinds of forms from now on.
We removed src/app/shared/address-forms in favor of src/app/shared/formly-address-forms and src/app/shared/forms-dynamic in favor of a generalized formly integration in src/app/shared/formly.
To implement your country-specific address forms in formly, see Forms.

We introduced an improved usage of memoized selectors for product selectors, split up state, saved additionally retrieved data in separate places, and migrated almost all product-related components to use the previously introduced product context facade (see changes #528).

From 0.26 to 0.27

We upgraded Cypress from Version 4 to 6 and followed all migrations in their Migration Guide.

We have introduced a Context Facade for product entities and refactored most of the components that are specific to a single product.
This includes:

  • Targeted components no longer require a product input, as they retrieve the product from the context.
  • The handling for adding products to the basket was refactored and simplified.
  • Product quantity handling moved almost completely to the context.
  • The decision for displaying certain components on product tiles and rows also moved into the context.

From 0.25 to 0.26

The project configuration was updated to use and test with Node.js version 14.15.0 LTS (including npm 6.14.8) for any further development.

We upgraded the Intershop PWA to use Angular 11.
With that a breaking change was introduced.
The RouterModule's relativeLinkResolution property changed from legacy to corrected.
We could not detect any impact for the PWA itself but custom code might have to be adapted.

We removed the Intershop PWA mock-data, as there are currently public servers provided for testing and exploring.
The handling for mocking REST API calls during development is hereby untouched.
The Angular CLI environment property mockServerAPI became obsolete, the property mustMockPaths was renamed to apiMockPaths.

From 0.24 to 0.25

We replaced the simple ngx-cookie-banner cookie banner with an own implementation that provides the means to configure and set more fine grained cookie consent options.
A basic configuration is already provided.
The cookie consent configuration and usage is documented in our Cookie Consent Guide.
With this change it is necessary to adapt all uses of the cookiesService.cookieLawSeen$ observable with the new synchronous method - cookiesService.cookieConsentFor('tracking') - provided to check for the required cookie consent.

We reworked the configuration format for setting up multiple channels in the nginx to enable context-path support.
Multiple PWA_X_ environment properties are no longer supported, instead a structured configuration has to be supplied.
For more information, see Nginx documentation.

From 0.23 to 0.24

We introduced a localization file clean up script that removes all unused localization keys from the localization files and sorts the remaining keys.
The clean up result is contained in a separate commit that should probably not be applied during a migration and instead a npm run clean-localizations should be performed on the project sources.

We renamed the testing helper findAllIshElements from ish-core/utils/dev/html-query-utils to findAllCustomElements to support project customization.
The returned lists from findAllCustomElements and findAllDataTestingIDs are no longer sorted to represent the actual template structure.

With Angular version 10.1, the testing utility async was deprecated.
We refactored our code base to use native async/await instead, which was possible in all cases.
The TSLint rule use-new-async-in-tests takes care of automatically transforming TestBed initialization code in component tests.
Other cases have to be refactored manually.

From 0.22 to 0.23

We removed deprecated exports related to the NgRx testing refactorings introduced in version 0.21.

We switched our main development to the new headless REST application type provided by ICM
If you are upgrading and want to continue using the Responsive Starter Store application types, do not cherry-pick the commits that switch application types.

We refactored the way ICM Http Errors are handled in the PWA.
You can read about it here.
Tests emulating HTTP errors now have to use the helper function makeHttpError from ish-core/utils/dev/api-service-utils.

We removed grouping folders of shared components in extensions and sub projects for a better overview.
You can migrate using the script node schematics/migration/0.22-to-0.23 (for running this script Git version 2.28 or above is recommended since earlier versions resulted in problems).

From 0.20 to 0.21

We deprecated and reworked the way of testing with NgRx.
The old format using ngrxTesting with combineReducers is now deprecated and replaced by the new approach.
The old testing mechanism will be removed in version 0.23.

We introduced a way to do shallow testing with feature toggles and used it in the tests.

We reorganized the core store:

  • new customer
    • store/addresses => store/customer/addresses
    • store/checkout/basket => store/customer/basket
    • store/orders => store/customer/orders
    • store/restore => store/customer/restore
    • store/user => store/customer/user
  • new core
    • store/configuration => store/core/configuration
    • store/error => store/core/error
    • store/messages => store/core/messages
    • store/router => store/core/router
    • store/viewconf => store/core/viewconf
  • new general
    • store/contact => store/general/contact
    • store/countries => store/general/countries
    • store/regions => store/general/regions

TSLint rules are set up to automatically fix imports, so run npm run check after upgrading.

In this version, we decided to start using the ngrx creator introduced in ngrx v8: createAction, createReducer and createEffect.
This means that the old way of writing action classes, reducer switch statements, and @effect() decorators is deprecated from 0.21 onwards.

Using these creator functions simplifies code and removes a lot of boiler plate from store files while providing type safety out-of-the-box.

You can automatically migrate your existing code by executing node schematics/migration/0.20-to-0.21.
Doing this will set related ts-lint rules and update each store or notify you of work previously needed.

From 0.19.1 to 0.20

We upgraded from Angular 8 to version 9 and activated the new rendering engine Ivy with this (following the official upgrade guide).
This was a major upgrade and comes with some changes:

  • The following changes are available for cherry-picking in one commit:

    • Angular no longer supports the previously deprecated string syntax for lazy loaded modules. Change it to the dynamic import format.

    • server.ts was partially rewritten to support SSR dev-server and serverless deployments. Building SSR is now supported by Angular CLI and explicit webpack builds were removed.

    • core-js had a major upgrade to version 3, so polyfill.ts imports have changed.

    • We temporarily replaced @ngx-utils/cookies with ngx-utils-cookies-port due to a bug when using Angular 9.1.

    • angular2-cookie-law was replaced by ngx-cookie-banner for compatibility reasons. This comes with a styling overhaul.

  • Further commits contain necessary refactoring:

    • TestBed.get in tests was deprecated in favor of the new type-safe TestBed.inject.

    • The empty generic type for NgRx Store is now the default and does not have to be supplied. The TSLint rule ngrx-use-empty-store-type was adapted to apply this refactoring.

    • We removed lazy loading with @wishtack/reactive-component-loader and replaced it with the native Angular 9 approach. If you have customized or created extensions, you will have to adapt the following:

      • Extension export modules are no longer imported and exported in SharedModule, instead export them in ShellModule.

      • Instead of pointing to the extension module with ReactiveComponentLoaderModule in the extension exports module, use the new provider for LAZY_FEATURE_MODULE pointing to the extension store module, if available. All further lazy loading is done by lazy components and lazy loaded pages. With this, the extension module should no longer import the extension store module.

      • Lazy components should no longer be part of the repository as they can be auto-generated on npm install. Use the new decorator @GenerateLazyComponent() via the lazy-component schematic to generate lazy components. We currently do not support creating lazy components for components with @Output() decorated fields.

      • Previous workarounds in <extension>-store.ts and <extension>-store.module.ts for adding reducers of selecting the feature state are no longer necessary and can be refactored to standard approaches.

    • We performed a major upgrade to prettier which comes with new code formatting for parts of the code.

    • We replaced VSCode extension stylelint-plus with the official extension. Update the recommended extensions.

    • We overhauled the integration of utility libraries for our custom schematics and TSLint rules. These libraries now get built when npm installing the PWA and transpiled JavaScript sources are no longer part of version control. Also, they mainly reuse libraries from the project root now.

From 0.18 to 0.19

We migrated from using ngrx-router to the official and better supported @ngrx/router-store.
This means that throughout the code all usage of the ofRoute operator and RouteNavigation actions are no longer available.

As some of these implementations were very specific, we cannot provide a migration script.

From 0.16 to 0.17

In this version change, we decided to no longer recommend the container-component-pattern and, therefore, changed the folder structure of the project.

We did this, because the previously introduced facades provide a more convenient way to interact with the state management and more and more logic was moved out of containers, hence removing all ngrx-related imports there.

You can run the migration by executing node schematics/migration/0.16-to-0.17.

The script will check if all your components can be moved to the new folder structure and will then perform the migration or notify you of work previously needed.

The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.
The Intershop Knowledge Portal uses only technically necessary cookies. We do not track visitors or have visitors tracked by 3rd parties. Please find further information on privacy in the Intershop Privacy Policy and Legal Notice.
Knowledge Base
Product Releases
Log on to continue
This Knowledge Base document is reserved for registered customers.
Log on with your Intershop Entra ID to continue.
Write an email to if you experience login issues,
or if you want to register as customer.