Skip to content

Releases: commercetools/merchant-center-application-kit

v23.0.0

19 Feb 16:28
1ab4a04
Compare
Choose a tag to compare

@commercetools-backend/[email protected]

Major Changes

  • #3530 18ace8a Thanks @emmenko! - Drop support for Node.js v16, which reached EOL. The minimal required version is v18 but we recommend to use v20 or v22 if possible, as v18 will also reach EOL mid of 2025.

  • #3530 18ace8a Thanks @emmenko! - Migrate to Vite v6. If you have Vite enabled via ENABLE_EXPERIMENTAL_VITE_BUNDLER and you are using vite as a dependency, make sure you upgrade to v6 (see Migration from v4 and Migration from v5).

@commercetools-backend/[email protected]

Major Changes

  • #3530 18ace8a Thanks @emmenko! - Drop support for Node.js v16, which reached EOL. The minimal required version is v18 but we recommend to use v20 or v22 if possible, as v18 will also reach EOL mid of 2025.

  • #3530 18ace8a Thanks @emmenko! - Migrate to Vite v6. If you have Vite enabled via ENABLE_EXPERIMENTAL_VITE_BUNDLER and you are using vite as a dependency, make sure you upgrade to v6 (see Migration from v4 and Migration from v5).

@commercetools-backend/[email protected]

Major Changes

  • #3530 18ace8a Thanks @emmenko! - Drop support for Node.js v16, which reached EOL. The minimal required version is v18 but we recommend to use v20 or v22 if possible, as v18 will also reach EOL mid of 2025.

  • #3530 18ace8a Thanks @emmenko! - Migrate to Vite v6. If you have Vite enabled via ENABLE_EXPERIMENTAL_VITE_BUNDLER and you are using vite as a dependency, make sure you upgrade to v6 (see Migration from v4 and Migration from v5).

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Major Changes

  • #3530 18ace8a Thanks @emmenko! - Drop support for Node.js v16, which reached EOL. The minimal required version is v18 but we recommend to use v20 or v22 if possible, as v18 will also reach EOL mid of 2025.

  • #3530 18ace8a Thanks @emmenko! - Migrate to Vite v6. If you have Vite enabled via ENABLE_EXPERIMENTAL_VITE_BUNDLER and you are using vite as a dependency, make sure you upgrade to v6 (see Migration from v4 and Migration from v5).

Patch Changes

@commercetools-frontend/[email protected]

Major Changes

  • #3530 18ace8a Thanks @emmenko! - Drop support for Node.js v16, which reached EOL. The minimal required version is v18 but we recommend to use v20 or v22 if possible, as v18 will also reach EOL mid of 2025.

  • #3530 18ace8a Thanks @emmenko! - Migrate to Vite v6. If you have Vite enabled via ENABLE_EXPERIMENTAL_VITE_BUNDLER and you are using vite as a dependency, make sure you upgrade to v6 (see Migration from v4 and Migration from v5).

Patch Changes

@commercetools-frontend/[email protected]

Major Changes

  • #3530 18ace8a Thanks @emmenko! - Drop support for Node.js v16, which reached EOL. The minimal required version is v18 but we recommend to use v20 or v22 if possible, as v18 will also reach EOL mid of 2025.

  • #3530 18ace8a Thanks @emmenko! - Migrate to Vite v6. If you have Vite enabled via ENABLE_EXPERIMENTAL_VITE_BUNDLER and you are using vite as a dependency, make sure you upgrade to v6 (see Migration from v4 and Migration from v5).

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Major Changes

  • #3530 18ace8a Thanks @emmenko! - Drop support for Node.js v16, which reached EOL. The minimal required version is v18 but we recommend to use v20 or v22 if possible, as v18 will also reach EOL mid of 2025.

  • #3530 18ace8a Thanks [@emmenko]...

Read more

v22.42.1

12 Feb 11:35
2a01552
Compare
Choose a tag to compare

@commercetools-backend/[email protected]

@commercetools-backend/[email protected]

@commercetools-backend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

v22.42.0

11 Feb 10:09
40ca1c9
Compare
Choose a tag to compare

@commercetools-backend/[email protected]

@commercetools-backend/[email protected]

Minor Changes

  • #3722 f4607a3 Thanks @emmenko! - Packages are built using the bundler option for TypeScript's moduleResolution.
    This is the recommended option for libraries to have more optimized bundles and have better compatibility.

    This also helps solving a compatibility issue with Emotion's version 11.14.0.

@commercetools-backend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Minor Changes

  • #3722 f4607a3 Thanks @emmenko! - Packages are built using the bundler option for TypeScript's moduleResolution.
    This is the recommended option for libraries to have more optimized bundles and have better compatibility.

    This also helps solving a compatibility issue with Emotion's version 11.14.0.

Patch Changes

@commercetools-frontend/[email protected]

Minor Changes

  • #3722 f4607a3 Thanks @emmenko! - Packages are built using the bundler option for TypeScript's moduleResolution.
    This is the recommended option for libraries to have more optimized bundles and have better compatibility.

    This also helps solving a compatibility issue with Emotion's version 11.14.0.

Patch Changes

@commercetools-frontend/[email protected]

Minor Changes

  • #3722 f4607a3 Thanks @emmenko! - Packages are built using the bundler option for TypeScript's moduleResolution.
    This is the recommended option for libraries to have more optimized bundles and have better compatibility.

    This also helps solving a compatibility issue with Emotion's version 11.14.0.

Patch Changes

@commercetools-frontend/[email protected]

Minor Changes

  • #3722 f4607a3 Thanks @emmenko! - Packages are built using the bundler option for TypeScript's moduleResolution.
    This is the recommended option for libraries to have more optimized bundles and have better compatibility.

    This also helps solving a compatibility issue with Emotion's version 11.14.0.

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Minor Changes

  • #3722 f4607a3 Thanks @emmenko! - Packages are built using the bundler option for TypeScript's moduleResolution.
    This is the recommended option for libraries to have more optimized bundles and have better compatibility.

    This also helps solving a compatibility issue with Emotion's version 11.14.0.

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Minor Changes

  • #3722 f4607a3 Thanks @emmenko! - Packages are built using the bundler option for TypeScript's moduleResolution.
    This is the recommended option for libraries to have more optimized bundles and have better compatibility.

    This also helps solving a compatibility issue with Emotion's version 11.14.0.

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Minor Changes

  • #3722 f4607a3 Thanks @emmenko! - Packages are built using the bundler option for TypeScript's moduleResolution.
    This is the recommended option for libraries to have more optimized bundles and have better compatibility.

    This also helps solving a compatibility issue with Emotion's version 11.14.0.

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Minor Changes

  • #3722 f4607a3 Thanks @emmenko! - Packages are built using the bundler option for TypeScript's moduleResolution.
    This is the recommended option for libraries to have more optimized bundles and have better compatibility.

    This also helps solving a compatibility issue with Emotion's version 11.14.0.

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Minor Changes

Read more

v22.41.0

04 Feb 14:06
0c2f3ae
Compare
Choose a tag to compare

@commercetools-backend/[email protected]

@commercetools-backend/[email protected]

@commercetools-backend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Minor Changes

  • #3710 fa5488a Thanks @kark! - Replace the usage of the react-modal library with @radix-ui/react-dialog for managing modals and dialogs.

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Minor Changes

  • #3710 fa5488a Thanks @kark! - Replace the usage of the react-modal library with @radix-ui/react-dialog for managing modals and dialogs.

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

v22.40.0

31 Jan 12:27
085b517
Compare
Choose a tag to compare

@commercetools-backend/[email protected]

@commercetools-backend/[email protected]

@commercetools-backend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Minor Changes

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

v22.39.1

27 Jan 13:01
19489da
Compare
Choose a tag to compare

@commercetools-backend/[email protected]

@commercetools-backend/[email protected]

@commercetools-backend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

  • #3709 c8ee91a Thanks @CarlosCortizasCT! - Remove the operation name query parameter we had introduced in the /graphql endpoint as it was forcing consumers to update part of their codebases.

    As an alternative we recommend using any browser extension that provides customized information for GraphQL requests (here's an example for Chromium based browsers).

  • Updated dependencies []:

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

  • #3707 09a4e2a Thanks @emmenko! - Make babel-plugin-formatjs opt-in via environment variable ENABLE_BABEL_PLUGIN_FORMATJS.

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

v22.39.0

23 Jan 11:44
3510f9b
Compare
Choose a tag to compare

@commercetools-backend/[email protected]

@commercetools-backend/[email protected]

@commercetools-backend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Minor Changes

  • #3689 f6827aa Thanks @mustafaasif2! - Update the mc-scripts config:sync command to synchronize submenu item order from the configuration file to the database.

  • #3705 8678e5e Thanks @valoriecarli! - Update build-vite script to output build files directly under the public folder

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

v22.38.3

21 Jan 16:20
6ece19a
Compare
Choose a tag to compare

@commercetools-backend/[email protected]

@commercetools-backend/[email protected]

@commercetools-backend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

v22.38.2

20 Jan 14:33
3ef7307
Compare
Choose a tag to compare

@commercetools-backend/[email protected]

@commercetools-backend/[email protected]

@commercetools-backend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

v22.38.1

13 Jan 09:27
2c15600
Compare
Choose a tag to compare

@commercetools-backend/[email protected]

@commercetools-backend/[email protected]

@commercetools-backend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]

Patch Changes

@commercetools-frontend/[email protected]