GraphCommerce 8.0.6

💡 This is a patch release, for the latest full release notes see the GraphCommerce 8.0 release notes ↩️

@graphcommerce/graphql-mesh@8.0.6

Patch Changes

• #2248 0289bfb - Suppress warning where a dependency is an expression, Added uglify-es and long as the dependencies couldn’t be found (@paales)

@graphcommerce/magento-cart-payment-method@8.0.6

Patch Changes

• #2248 e262419 - Compatibility with Magento 2.4.7 (@paales)

@graphcommerce/next-config@8.0.6

Patch Changes

• #2248 0289bfb - reduce bundlesize of @apollo/client (@paales)

• #2248 0289bfb - Suppress warning where a dependency is an expression, Added uglify-es and long as the dependencies couldn’t be found (@paales)

May 06, 2024 (canary)

@graphcommerce/next-config@8.1.0-canary.12

• Make labels translatable

May 02, 2024 (canary)

@graphcommerce/magento-product@8.1.0-canary.11

Patch Changes

• #2255 679d07d - make the ProductPageMeta fragment injectable
  (@carlocarels90)

April 30, 2024 (canary)

@graphcommerce/next-config@8.1.0-canary.10

Patch Changes

• #2251 bc6a9b4 - When creating a release PR, make sure it is created against the main branch so it can be directly merged.
  (@paales)

April 30, 2024 (canary)

@graphcommerce/docs@8.1.0-canary.9

Patch Changes

• #2223 7652234 - Replaced next-sitemap with page router based robots.txt & sitemaps
  (@bramvanderholst)

@graphcommerce/graphcms-ui@8.1.0-canary.9

Patch Changes

• #2223 0ccec63 - Added helper method to get Hygraph paths
  (@bramvanderholst)

@graphcommerce/next-ui@8.1.0-canary.9

Patch Changes

• #2223 d7459fe - Updated canonicalize helper for better multi domain support
  (@bramvanderholst)

@graphcommerce/next-config@8.1.0-canary.9

Patch Changes

• #2223 4f7fe02 - Added robotsAllow to storefront config
  (@bramvanderholst)

April 29, 2024 (canary)

@graphcommerce/docs@8.1.0-canary.8

Patch Changes

• #2247 444e446 - Added clear upgrade instructions for linguiLocale
  (@paales)

@graphcommerce/cli@8.1.0-canary.8

Patch Changes

• #2247 cfc0f4e - Make sure the interceptors are generated before the typecheck is ran.
  (@paales)

@graphcommerce/graphql-mesh@8.1.0-canary.8

Patch Changes

• #2247 6831040 - Suppress warning where a dependency is an expression, Added uglify-es and long as the dependencies couldn’t be found
  (@paales)

@graphcommerce/lingui-next@8.1.0-canary.8

Patch Changes

• #2247 444e446 - Added clear upgrade instructions for linguiLocale
  (@paales)

@graphcommerce/magento-cart@8.1.0-canary.8

Patch Changes

• #2247 a56a7c6 - Solve an issue where the cart would be sometimes undefined, but Partial was too eleborate
  (@paales)

@graphcommerce/magento-cart-payment-method@8.1.0-canary.8

Patch Changes

• #2247 d345474 - Due to a cyclic dependency the actual PaymentMethodPlaceOrder button would sometimes be undefined.
  (@paales)

@graphcommerce/magento-product-configurable@8.1.0-canary.8

Patch Changes

• #2247 444e446 - Added clear upgrade instructions for linguiLocale
  (@paales)

@graphcommerce/next-ui@8.1.0-canary.8

Patch Changes

• #2247 444e446 - Added clear upgrade instructions for linguiLocale
  (@paales)

@graphcommerce/next-config@8.1.0-canary.8

Patch Changes

• #2247 5153904 - Added PRIVATE_ADDITIONAL_DEPENDENCIES to enable packages that we do not want to have in the examples directory but we do want to be able to demo.
  (@paales)

• #2247 6831040 - reduce bundlesize of @apollo/client
  (@paales)

• #2247 81c6c81 - Solved an issue where the plugins would be generated with the wrong path
  (@paales)

• #2247 6831040 - Suppress warning where a dependency is an expression, Added uglify-es and long as the dependencies couldn’t be found
  (@paales)

• #2247 cfc0f4e - Make sure the interceptors are generated before the typecheck is ran.
  (@paales)

• #2247 444e446 - Added clear upgrade instructions for linguiLocale
  (@paales)

• #2247 3f9d8f5 - Added better interceptor comments and link to original files
  (@paales)

April 23, 2024 (canary)

@graphcommerce/googlerecaptcha@8.1.0-canary.7

Patch Changes

• #2245 898224c - Solve an issue where the grecaptcha.execute method would throw ‘null’ causing the checkout to break in unexpected ways.
  (@paales)

April 23, 2024 (canary)

@graphcommerce/docs@8.1.0-canary.6

Patch Changes

• #1984 e05534f - Added docs about caching
  (@paales)

April 22, 2024 (canary)

@graphcommerce/magento-product@8.1.0-canary.5

Patch Changes

• #2224 4dd2d01 - When applying a filter it would not always scroll to the #products.
  (@FrankHarland)

@graphcommerce/next-config@8.1.0-canary.5

Minor Changes

• #2226 8939df2 - Big improvements to the plugin system: Typescript validated, deeper resolution, new configuration object, replace plugins, and more ifConfig options.

  1. Plugins now use TypeScript's "moduleSuffixes": [".interceptor", ""] functionality which means that plugins now correctly resolve via TypeScript. So if you go to reference in VSCode (or any other editor), you go to the interceptor directly and see which plugins are applied there. This also means that plugins are automatically checked during build (and will fail if there are errors).

  2. The exported type of an intercepted component now has the types of all plugins applied. This means that plugins can modify the props of components (and is still validated with TypeScript). To make this work a plugin must always forward props to the <Prev> to ensure that values are correctly passed on.

  3. Plugins will now always be applied to deepest resolved path. This means that a plugin automatically applies to internal usages as well. This thus means that plugins do not need to be written with an internal path, but can keep the parent path. Istead of writing @graphcommerce/magento-cart-items/components/RemoveItemFromCart/RemoveItemFromCartFab you can now write @graphcommerce/magento-cart-items.

  4. A new configuration object for plugins is created instead of separate exports (the legacy format is still supported though):

     export const config: PluginConfig = {
       type: 'component'
       module: '@graphcommerce/magento-product',
       ifConfig: 'demoMode',
     }

     This also means that the name of the export dictates the name of the component/function the plugin is applied.

  5. We now support replace plugins (type: 'replace'), which allow you to replace the original component/function/const completely (and type checked of course).

     import { ProductPageNameProps } from "@graphcommerce/magento-product";
     import { PluginConfig } from "@graphcommerce/next-config";
     
     export const config: PluginConfig = {
       type: "replace",
       module: "@graphcommerce/magento-product",
     };
     
     export function ProductPageName(props: ProductPageNameProps) {
       const { product } = props;
       return <div>REPLACEMENT {product.url_key}</div>;
     }

     Plugin files can now have multiple exports for the same configuration. So next to the ProductPageName you can also have a ProductPagePrice export for example in the same file.

  6. We now support ifConfig tuple which allows you to apply a plugin only if a certain configuration is set.

     export const config: PluginConfig = {
       type: "replace",
       module: "@graphcommerce/magento-product",
       ifConfig: ["theme", "my-theme"],
     };

     This allows you to support multiple builds with different plugins applied. For example one build with GC_THEME=my-theme and another with GC_THEME=my-other-theme. (@paales)

April 22, 2024 (canary)

@graphcommerce/magento-category@8.0.6-canary.4

Patch Changes

• #2227 d597719 - Added option to change sort order (ASC / DESC) for sort options (Name, price, position etc) on catalog and search pages.
  (@FrankHarland)

@graphcommerce/magento-product@8.0.6-canary.4

Patch Changes

• #2227 d597719 - Added option to change sort order (ASC / DESC) for sort options (Name, price, position etc) on catalog and search pages.
  (@FrankHarland)

@graphcommerce/next-config@8.0.6-canary.4

Patch Changes

• #2227 d597719 - Added option to change sort order (ASC / DESC) for sort options (Name, price, position etc) on catalog and search pages.
  (@FrankHarland)