graphcommerce | GraphQL Ecosystem Directory

graphcommerce - May 23, 2024 (canary)

Published by github-actions[bot] 5 months ago

@graphcommerce/[email protected]

Patch Changes

#2264 e5291a4 - prevent rendering 'null' when method_title is not provided
(@carlocarels90)

graphcommerce - May 22, 2024 (canary)

Published by github-actions[bot] 5 months ago

@graphcommerce/[email protected]

Patch Changes

#2277 f9199f7 - Solve issue where Braintree wouldn't place the order after successfully validating a Credit Card.
(@paales)

@graphcommerce/[email protected]

Patch Changes

#2277 f9199f7 - Solve issue where Braintree wouldn't place the order after successfully validating a Credit Card.
(@paales)

graphcommerce - May 22, 2024 (canary)

Published by github-actions[bot] 5 months ago

@graphcommerce/[email protected]

Minor Changes

#2209 2872cab - Removed useMediaQuery from the wishlist and cart ItemActionCard and replaced it with a new responsive size prop.
(@Jessevdpoel)

@graphcommerce/[email protected]

Minor Changes

#2209 2872cab - Removed useMediaQuery from the wishlist and cart ItemActionCard and replaced it with a new responsive size prop.
(@Jessevdpoel)

@graphcommerce/[email protected]

Minor Changes

#2209 2872cab - Removed useMediaQuery from the wishlist and cart ItemActionCard and replaced it with a new responsive size prop.
(@Jessevdpoel)

graphcommerce - May 22, 2024 (canary)

Published by github-actions[bot] 5 months ago

@graphcommerce/[email protected]

Patch Changes

#2275 29e496c - Prevent ScrollerThumbnail from scrolling the page horizontally
(@Giovanni-Schroevers)

@graphcommerce/[email protected]

graphcommerce - May 17, 2024 (canary)

Published by github-actions[bot] 5 months ago

@graphcommerce/[email protected]

Patch Changes

#2267 9d5fd11 - make the CategoryHeroNav fragment injectable and add image to the childeren
(@carlocarels90)

graphcommerce - May 17, 2024 (canary)

Published by github-actions[bot] 5 months ago

@graphcommerce/[email protected]

Patch Changes

831d7cd - Compatibility with Magento 2.4.7
(@paales)

graphcommerce - GraphCommerce 8.0.6

Published by github-actions[bot] 5 months ago

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

@graphcommerce/[email protected]

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/[email protected]

Patch Changes

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

@graphcommerce/[email protected]

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)

graphcommerce - May 06, 2024 (canary)

Published by github-actions[bot] 6 months ago

@graphcommerce/[email protected]

Make labels translatable

graphcommerce - May 02, 2024 (canary)

Published by github-actions[bot] 6 months ago

@graphcommerce/[email protected]

Patch Changes

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

graphcommerce - April 30, 2024 (canary)

Published by github-actions[bot] 6 months ago

@graphcommerce/[email protected]

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)

graphcommerce - April 30, 2024 (canary)

Published by github-actions[bot] 6 months ago

@graphcommerce/[email protected]

Patch Changes

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

@graphcommerce/[email protected]

Patch Changes

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

@graphcommerce/[email protected]

Patch Changes

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

@graphcommerce/[email protected]

Patch Changes

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

graphcommerce - April 29, 2024 (canary)

Published by github-actions[bot] 6 months ago

@graphcommerce/[email protected]

Patch Changes

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

@graphcommerce/[email protected]

Patch Changes

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

@graphcommerce/[email protected]

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/[email protected]

Patch Changes

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

@graphcommerce/[email protected]

Patch Changes

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

@graphcommerce/[email protected]

Patch Changes

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

@graphcommerce/[email protected]

Patch Changes

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

@graphcommerce/[email protected]

Patch Changes

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

@graphcommerce/[email protected]

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)

graphcommerce - April 23, 2024 (canary)

Published by github-actions[bot] 6 months ago

@graphcommerce/[email protected]

Patch Changes

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

graphcommerce - April 23, 2024 (canary)

Published by github-actions[bot] 6 months ago

@graphcommerce/[email protected]

Patch Changes

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

graphcommerce - April 22, 2024 (canary)

Published by github-actions[bot] 6 months ago

@graphcommerce/[email protected]

Patch Changes

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

@graphcommerce/[email protected]

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)

graphcommerce - April 22, 2024 (canary)

Published by github-actions[bot] 6 months ago

@graphcommerce/[email protected]

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/[email protected]

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/[email protected]

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 - April 22, 2024 (canary)

Published by github-actions[bot] 6 months ago

@graphcommerce/[email protected]

Patch Changes

#2219 2ed2055 - Allow blog pages to be nested
(@Jessevdpoel)

graphcommerce - April 22, 2024 (canary)

Published by github-actions[bot] 6 months ago

@graphcommerce/[email protected]

Patch Changes

#2234 0767bc4 - Upgrade input components to no longer use muiRegister, which improves INP scores
(@FrankHarland)
#2234 43bd04a - Make sure the TextFieldElement doesn’t give a uncontrolled to controlled warning.
Convert SelectElement to useController instead of a separate Controller component.
Make sure the original endAdornment is always shown only until the value is valid (@FrankHarland)
#2234 d4e693d - The <WaitForQueries/> component now uses the useIsSSR hook which prevents loading spinners when navigating on the client, which make all account/cart/checkout pages faster.
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 43bd04a - Prevent BillingPage query from rerunning on each mutation
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 0767bc4 - Upgrade input components to no longer use muiRegister, which improves INP scores
(@FrankHarland)
#2234 530076e - Moved all usages of useFormPersist to the component to prevent rerenders.
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 0767bc4 - Upgrade input components to no longer use muiRegister, which improves INP scores
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 0767bc4 - Upgrade input components to no longer use muiRegister, which improves INP scores
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 43bd04a - Use the non resolved payment methods as a placeholder for the actual payment methods
(@FrankHarland)
#2234 530076e - Moved all usages of useFormPersist to the component to prevent rerenders.
(@FrankHarland)
#2234 43bd04a - Prevent BillingPage query from rerunning on each mutation
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 0767bc4 - Upgrade input components to no longer use muiRegister, which improves INP scores
(@FrankHarland)
#2234 530076e - Moved all usages of useFormPersist to the component to prevent rerenders.
(@FrankHarland)
#2234 43bd04a - The billing and shipping address of a customer would not be recognized as the same address although they would effectively be the same
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 530076e - Moved all usages of useFormPersist to the component to prevent rerenders.
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 530076e - Moved all usages of useFormPersist to the component to prevent rerenders.
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 0767bc4 - Upgrade input components to no longer use muiRegister, which improves INP scores
(@FrankHarland)
#2234 530076e - Moved all usages of useFormPersist to the component to prevent rerenders.
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 530076e - Moved all usages of useFormPersist to the component to prevent rerenders.
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 0767bc4 - Upgrade input components to no longer use muiRegister, which improves INP scores
(@FrankHarland)
#2234 530076e - Moved all usages of useFormPersist to the component to prevent rerenders.
(@FrankHarland)
#2234 43bd04a - Prevent BillingPage query from rerunning on each mutation
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 43bd04a - Prevent BillingPage query from rerunning on each mutation
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 0767bc4 - Upgrade input components to no longer use muiRegister, which improves INP scores
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 530076e - Moved all usages of useFormPersist to the component to prevent rerenders.
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 0767bc4 - Upgrade input components to no longer use muiRegister, which improves INP scores
(@FrankHarland)
#2234 43bd04a - Prevent BillingPage query from rerunning on each mutation
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 0767bc4 - Upgrade input components to no longer use muiRegister, which improves INP scores
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 0767bc4 - Upgrade input components to no longer use muiRegister, which improves INP scores
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 530076e - Moved all usages of useFormPersist to the component to prevent rerenders.
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 43bd04a - Added useIsSSR hook that will properly resolve when the page is rendered on the server and on first render, but will return false when a component is rendered on the client directly.
(@FrankHarland)
#2234 0767bc4 - Upgrade input components to no longer use muiRegister, which improves INP scores
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 43bd04a - Add deprecation warnings for useFormMuiRegister. Refactor useFormPersist to useWatch and add a separate <FormPersist/> component to prevent rerenders.
(@FrankHarland)
#2234 0767bc4 - Upgrade input components to no longer use muiRegister, which improves INP scores
(@FrankHarland)
#2234 02da217 - Migrate most usages of useFormAutoSubmit to and deprecated useFormAutoSubmit
(@FrankHarland)
#2234 530076e - Moved all usages of useFormPersist to the component to prevent rerenders.
(@FrankHarland)
#2234 1a6d0c4 - Mark useFormValidFields as deprecated: Please use TextInputElement, SelectElement, etc. with the showValid prop
(@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

#2234 0767bc4 - Upgrade input components to no longer use muiRegister, which improves INP scores
(@FrankHarland)

graphcommerce - April 22, 2024 (canary)

Published by github-actions[bot] 6 months ago

@graphcommerce/[email protected]

Patch Changes

#2213 a0d952e - Moved product reviews to the relatedUpsells query so we do not pass the queryComplexity limit
(@paales)

@graphcommerce/[email protected]

Patch Changes

#2213 a0d952e - Moved product reviews to the relatedUpsells query so we do not pass the queryComplexity limit
(@paales)

@graphcommerce/[email protected]

Patch Changes

#2213 9b8349f - Removed the ProductPage query from the examples directory as it isn't used anymore
(@paales)

graphcommerce - April 22, 2024 (canary)

Published by github-actions[bot] 6 months ago

@graphcommerce/[email protected]

Patch Changes

#2196 84c50e4 - Allow Lingui to use linguiLocale with country identifiers like en-us, it would always load en in this case. Introced a new useLocale hook to use the correct locale string to use in Intl methods.
(@paales)

@graphcommerce/[email protected]

Patch Changes

#2196 84c50e4 - Allow Lingui to use linguiLocale with country identifiers like en-us, it would always load en in this case. Introced a new useLocale hook to use the correct locale string to use in Intl methods.
(@paales)

@graphcommerce/[email protected]

Patch Changes

#2196 84c50e4 - Allow Lingui to use linguiLocale with country identifiers like en-us, it would always load en in this case. Introced a new useLocale hook to use the correct locale string to use in Intl methods.
(@paales)

@graphcommerce/[email protected]

Patch Changes

#2196 84c50e4 - Allow Lingui to use linguiLocale with country identifiers like en-us, it would always load en in this case. Introced a new useLocale hook to use the correct locale string to use in Intl methods.
(@paales)

@graphcommerce/[email protected]

Patch Changes

#2196 84c50e4 - Allow Lingui to use linguiLocale with country identifiers like en-us, it would always load en in this case. Introced a new useLocale hook to use the correct locale string to use in Intl methods.
(@paales)

@graphcommerce/[email protected]

Patch Changes

#2196 84c50e4 - Allow Lingui to use linguiLocale with country identifiers like en-us, it would always load en in this case. Introced a new useLocale hook to use the correct locale string to use in Intl methods.
(@paales)