chore: Update all non-major dependencies - #280

v7.4.1

Compare Source

Patch Changes

• #​10935
  fb1a7c4
  Thanks @​eddeee888! - dependencies updates:

  • Updated dependency
    @graphql-tools/code-file-loader@^8.1.39 ↗︎
    (from ^8.1.28, in dependencies)

• #​10942
  57c3e7b
  Thanks @​eddeee888! - dependencies updates:

  • Updated dependency
    @graphql-tools/merge@^9.2.4 ↗︎
    (from ^9.0.6, in dependencies)

• #​10942
  57c3e7b
  Thanks @​eddeee888! - Bump @graphql-tools/merge from ^9.0.6 to
  ^9.2.4.

• #​10935
  fb1a7c4
  Thanks @​eddeee888! - Fix a Windows-specific import() failure on
  absolute paths when loading a schema/document from a .js/.cjs/.mjs file (via
  @graphql-tools/code-file-loader), and when loading modules passed to that loader's own require
  option. Node's dynamic import() rejects raw absolute Windows paths (the drive letter is parsed
  as a URL scheme). Fixed by bumping @graphql-tools/code-file-loader to 8.1.39, which contains
  the upstream fix
  (ardatan/graphql-tools#8421).

• #​10936
  9521c0c
  Thanks @​eddeee888! - Fix watch mode's generated ignore glob
  patterns using the platform path separator (\ on Windows), which @parcel/watcher never
  matched, so generated output files were watched (and could re-trigger builds) instead of being
  ignored. Ignore patterns are now always forward-slash, as @parcel/watcher expects.

  Also fixes the test suite's TempDir.clean() helper on Windows, where rimraf.sync() rejected
  its own glob-style cleanup pattern as containing illegal path characters; now passes
  { glob: true }. This is a test-only change (tests/utils.ts is not part of the published
  package) included here since it was needed to get the suite green on Windows alongside the
  watch-mode fix.

v7.4.0

Compare Source

Minor Changes

• #​10928
  90229a5
  Thanks @​eddeee888! - Add
  contentComparison?: 'cache-first' | 'disk' to control disk-vs-cache write comparison in watch
  mode.

  In watch mode the CLI caches the hash of the content it last wrote per file and compares new
  output against that cached hash to skip redundant writes. This assumes generated output is a pure
  function of the codegen inputs. An output whose content depends on the file's existing content
  (e.g. a preset that reads the file and rewrites part of it) breaks that assumption: if the file is
  changed on disk and codegen regenerates content identical to a previous run, the cached hash still
  matches and the write is skipped, so the on-disk change is never corrected.

  contentComparison: 'disk' opts an output into comparing the generated content against the file
  on disk instead of the in-memory record of what codegen last wrote, so the file is rewritten when
  it was changed externally. It can be set:

  • by a preset, on the GenerateOptions it returns from buildGeneratesSection, or
  • on the output config (generates[output].contentComparison) for any output, including plain
    plugin outputs without a preset.

  When both are present, the preset's value takes precedence. The default, 'cache-first', keeps
  the existing in-memory-cache behaviour for outputs that are a pure function of their inputs.

Patch Changes

• #​10930
  448431a
  Thanks @​eddeee888! - Fix overwrite being ignored for
  preset-based generates outputs.

  A generates entry that used a preset and set overwrite (e.g.
  overwrite: { removeStaleFiles: false }) had that setting silently ignored, so in watch mode its
  generated files could still be deleted as stale.

  The CLI resolved overwrite per generated file by looking the file's path up in
  config.generates. That fails for a preset: its generates entry is keyed by the preset's
  baseOutputDir, not by any generated file's path (and a preset can emit files outside that
  directory), and the lookup additionally required a plugins key that preset entries don't have.
  Both cases fell through to the global config.overwrite (default true).

• Updated dependencies
  [90229a5,
  448431a]:

  • @​graphql-codegen/plugin-helpers@7.3.0

v7.3.0

Compare Source

Minor Changes

• #​10928
  90229a5
  Thanks @​eddeee888! - Add
  contentComparison?: 'cache-first' | 'disk' to control disk-vs-cache write comparison in watch
  mode.

  In watch mode the CLI caches the hash of the content it last wrote per file and compares new
  output against that cached hash to skip redundant writes. This assumes generated output is a pure
  function of the codegen inputs. An output whose content depends on the file's existing content
  (e.g. a preset that reads the file and rewrites part of it) breaks that assumption: if the file is
  changed on disk and codegen regenerates content identical to a previous run, the cached hash still
  matches and the write is skipped, so the on-disk change is never corrected.

  contentComparison: 'disk' opts an output into comparing the generated content against the file
  on disk instead of the in-memory record of what codegen last wrote, so the file is rewritten when
  it was changed externally. It can be set:

  • by a preset, on the GenerateOptions it returns from buildGeneratesSection, or
  • on the output config (generates[output].contentComparison) for any output, including plain
    plugin outputs without a preset.

  When both are present, the preset's value takes precedence. The default, 'cache-first', keeps
  the existing in-memory-cache behaviour for outputs that are a pure function of their inputs.

Patch Changes

• #​10930
  448431a
  Thanks @​eddeee888! - Fix overwrite being ignored for
  preset-based generates outputs.

  A generates entry that used a preset and set overwrite (e.g.
  overwrite: { removeStaleFiles: false }) had that setting silently ignored, so in watch mode its
  generated files could still be deleted as stale.

  The CLI resolved overwrite per generated file by looking the file's path up in
  config.generates. That fails for a preset: its generates entry is keyed by the preset's
  baseOutputDir, not by any generated file's path (and a preset can emit files outside that
  directory), and the lookup additionally required a plugins key that preset entries don't have.
  Both cases fell through to the global config.overwrite (default true).

v8.1.39

Compare Source

Patch Changes

• #​8421 89e78a5 Thanks @​ardatan! - Convert absolute filesystem paths to file:// URLs before dynamic import() in the ESM build so schema/document loading works on native Windows, while leaving raw paths for the CJS build where import() is downleveled to require(). Closes #​8420.

v8.1.38

Compare Source

Patch Changes

• Updated dependencies [1c1c5a0, 1c1c5a0, 60db079, 57e316d, 1c1c5a0, 1c1c5a0, 0b9529f]:
  • @​graphql-tools/graphql-tag-pluck@8.3.37
  • @​graphql-tools/utils@12.0.1

v8.3.37

Compare Source

Patch Changes

• #​8370 1c1c5a0 Thanks @​ardatan! - dependencies updates:

  • Removed dependency @babel/plugin-syntax-import-assertions@^7.26.0 ↗︎ (from dependencies)

• #​8370 1c1c5a0 Thanks @​ardatan! - Parse with Babel importAttributes (and deprecatedAssertSyntax so existing assert { … } files still work), and drop the unused @babel/plugin-syntax-import-assertions dependency. Fixes #​5454.

• Updated dependencies [60db079, 57e316d, 1c1c5a0, 1c1c5a0, 0b9529f]:

  • @​graphql-tools/utils@12.0.1

v4.3.2

Compare Source

v4.3.2 is the next patch release.

👉 Changelog

compare changes

🩹 Fixes

• vitest-environment: keep vitest/environments import opaque to rolldown (6d1195d38)

❤️ Contributors

• Daniel Roe (@​danielroe)

v4.3.1

Compare Source

v4.3.1 is the next patch release.

👉 Changelog

compare changes

🩹 Fixes

• deps: allow vitest ^5 as peer dependency (#​1809)

🏡 Chore

• force lf for pnpm patches (e68ecfa28)

🎉 New Contributors

• Benjamin Canac (@​benjamincanac)

❤️ Contributors

• Daniel Roe (@​danielroe)
• Benjamin Canac (@​benjamincanac)

v4.3.0

Compare Source

v4.3.0 is the next minor release.

👉 Changelog

compare changes

🚀 Enhancements

• runtime-utils: add unmockNuxtImport helper (#​1795)
• config: support vitest 5 (#​1802)

🩹 Fixes

• config: default nuxt test pattern to nested for simple non-nuxt setup (#​1801)

✅ Tests

• make sure tests are collected at runtime, not statically (#​1797)

🎉 New Contributors

• Vladimir (@​sheremet-va)

❤️ Contributors

• Yoshihiro Yamaguchi (@​yamachi4416)
• Vladimir (@​sheremet-va)

v4.11.1

Compare Source

Bug Fixes

• ChatMessages: add missing color to user and assistant props (#​6920) (bbf1e14)
• Checkbox/RadioGroup: add flex-wrap on list and card variants (#​6913) (90c45a6)
• Checkbox/RadioGroup: use border-default on card and table variants (#​6884) (9bdb89b)
• CommandPalette: keep astral characters intact when truncating search results (#​6817) (e4cb042)
• Form: omit method attribute on nested forms (#​6888) (a494a97)
• InputNumber: work uncontrolled with only a default value (#​6859) (2d4782b)
• Link: restore prefetching with Nuxt 4.5 custom slot (#​6921) (c4ee0ea)
• Link: wait for onNuxtReady before observing visibility (#​6922) (612ab1c)
• NavigationMenu: avoid duplicate accordion trigger on items without to (#​6862) (726e142)
• ProseCodeTree: invoke default slot from render (#​6906) (fbb9e22)
• Select/SelectMenu: add responsive text size (#​6903) (e791d30)
• SelectMenu: prevent search input focus on open with autofocus: false (#​6905) (6caa6a9)
• Slider: emit a number for a single thumb (#​6890) (3d2de0c)
• Table: exclude hidden columns from colspan (#​6894) (2e8f533)

v0.10.1

Compare Source

v0.10.1 is the next patch release.

👉 Changelog

compare changes

🩹 Fixes

• inline beasties runtime into the server bundle (03f3ec8)

❤️ Contributors

• Daniel Roe (@​danielroe)

v0.10.0

Compare Source

v0.10.0 is the next major release.

👉 Changelog

compare changes

🚀 Enhancements

• ⚠️ use beasties build-time compiler and zero-dependency runtime (#​702)

🤖 CI

• add explicit permissions (fd9b88f)
• add agent-scan workflow to flag bot-authored PRs (ced5dc5)

❤️ Contributors

• Daniel Roe (@​danielroe)

v2024.10.2

Compare Source

Patch Changes

• This version adds support for the new cookie system in Shopify (_shopify_analytics and _shopify_marketing http-only cookies). It is backward compatible and still supports the deprecated _shopify_y and _shopify_s cookies. (#​3342) by @​kdaviduik

  • createRequestHandler can now be used for every Hydrogen app, not only the ones deployed to Oxygen. It is now exported from @shopify/hydrogen.
  • A new Storefront API proxy is now available in Hydrogen's createRequestHandler. This will be used to obtain http-only cookies from Storefront API. In general, it should be transparent but it can be disabled with the proxyStandardRoutes option.
  • Analytics.Provider component and useCustomerPrivacy hook now make a request internally to the mentioned proxy to obtain cookies in the storefront domain.

• Fixed a number of issues related to irregular behaviors between Privacy Banner and Hydrogen's analytics events. (#​3342) by @​kdaviduik

• Updated dependencies [ab7d896c]:

  • @​shopify/hydrogen-react@2024.10.2

v2024.10.1

Compare Source

Patch Changes

• Added namespace support to prevent conflicts when using multiple Pagination components: (#​2649) by @​scottdixon

  • New optional namespace prop for the <Pagination/> component
  • New optional namespace option for getPaginationVariables() utility
  • When specified, pagination URL parameters are prefixed with the namespace (e.g., products_cursor instead of cursor)
  • Maintains backwards compatibility when no namespace is provided

• Introduce getProductOptions, getAdjacentAndFirstAvailableVariants, useSelectedOptionInUrlParam, and mapSelectedProductOptionToObject to support combined listing products and products with 2000 variants limit. (#​2659) by @​wizardlyhel

• Add params to override the login and authorize paths: (#​2648) by @​blittle

  const hydrogenContext = createHydrogenContext({
    // ...
    customerAccount: {
      loginPath = '/account/login',
      authorizePath = '/account/authorize',
      defaultRedirectPath = '/account',
    },
  });

• Add selectedVariant prop to the VariantSelector to use for the initial state if no URL parameters are set (#​2643) by @​scottdixon

• Updated dependencies [a57d5267]:

  • @​shopify/hydrogen-react@2024.10.1

v2024.10.0

Compare Source

Patch Changes

• Add optional headers param for logout redirect (#​2602) by @​coryagami

• Stabilize getSitemap, getSitemapIndex and implement on skeleton (#​2589) by @​juanpprieto

  1. Update the getSitemapIndex at /app/routes/[sitemap.xml].tsx

  - import {unstable__getSitemapIndex as getSitemapIndex} from '@shopify/hydrogen';
  + import {getSitemapIndex} from '@shopify/hydrogen';

  2. Update the getSitemap at /app/routes/sitemap.$type.$page[.xml].tsx

  - import {unstable__getSitemap as getSitemap} from '@shopify/hydrogen';
  + import {getSitemap} from '@shopify/hydrogen';

  For a reference implementation please see the skeleton template sitemap routes

• Update <ProductPrice> to remove deprecated code usage for priceV2 and compareAtPriceV2. Remove export for getCustomerPrivacy. (#​2601) by @​wizardlyhel

• [Breaking change] (#​2588) by @​wizardlyhel

  Set up Customer Privacy without the Shopify's cookie banner by default.

  If you are using Shopify's cookie banner to handle user consent in your app, you need to set withPrivacyBanner: true to the consent config. Without this update, the Shopify cookie banner will not appear.

    return defer({
      ...
      consent: {
        checkoutDomain: env.PUBLIC_CHECKOUT_DOMAIN,
        storefrontAccessToken: env.PUBLIC_STOREFRONT_API_TOKEN,
  +      withPrivacyBanner: true,
        // localize the privacy banner
        country: args.context.storefront.i18n.country,
        language: args.context.storefront.i18n.language,
      },
    });

• Update to 2024-10 SFAPI (#​2570) by @​wizardlyhel

• [Breaking change] (#​2546) by @​frandiox

  Update createWithCache to make it harder to accidentally cache undesired results. request is now mandatory prop when initializing createWithCache.

  // server.ts
  export default {
    async fetch(
      request: Request,
      env: Env,
      executionContext: ExecutionContext,
    ): Promise<Response> {
      try {
        // ...
  -     const withCache = createWithCache({cache, waitUntil});
  +     const withCache = createWithCache({cache, waitUntil, request});

  createWithCache now returns an object with two utility functions: withCache.run and withCache.fetch. Both have a new prop shouldCacheResult that must be defined.

  The original withCache callback function is now withCache.run. This is useful to run multiple fetch calls and merge their responses, or run any arbitrary code. It caches anything you return, but you can throw if you don't want to cache anything.

    const withCache = createWithCache({cache, waitUntil, request});
  
    const fetchMyCMS = (query) => {
  -    return withCache(['my-cms', query], CacheLong(), async (params) => {
  +    return withCache.run({
  +      cacheKey: ['my-cms', query],
  +      cacheStrategy: CacheLong(),
  +      // Cache if there are no data errors or a specific data that make this result not suited for caching
  +      shouldCacheResult: (result) => !result?.errors,
  +    }, async(params) => {
        const response = await fetch('my-cms.com/api', {
          method: 'POST',
          body: query,
        });
        if (!response.ok) throw new Error(response.statusText);
        const {data, error} = await response.json();
        if (error || !data) throw new Error(error ?? 'Missing data');
        params.addDebugData({displayName: 'My CMS query', response});
        return data;
      });
    };

  New withCache.fetch is for caching simple fetch requests. This method caches the responses if they are OK responses, and you can pass shouldCacheResponse, cacheKey, etc. to modify behavior. data is the consumed body of the response (we need to consume to cache it).

  const withCache = createWithCache({cache, waitUntil, request});
  
  const {data, response} = await withCache.fetch<{data: T; error: string}>(
    'my-cms.com/api',
    {
      method: 'POST',
      headers: {'Content-type': 'application/json'},
      body,
    },
    {
      cacheStrategy: CacheLong(),
      // Cache if there are no data errors or a specific data that make this result not suited for caching
      shouldCacheResponse: (result) => !result?.error,
      cacheKey: ['my-cms', body],
      displayName: 'My CMS query',
    },
  );

• [Breaking change] (#​2585) by @​wizardlyhel

  Deprecate usages of product.options.values and use product.options.optionValues instead.

  1. Update your product graphql query to use the new optionValues field.

    const PRODUCT_FRAGMENT = `#graphql
      fragment Product on Product {
        id
        title
        options {
          name
  -        values
  +        optionValues {
  +          name
  +        }
        }

  2. Update your <VariantSelector> to use the new optionValues field.

    <VariantSelector
      handle={product.handle}
  -    options={product.options.filter((option) => option.values.length > 1)}
  +    options={product.options.filter((option) => option.optionValues.length > 1)}
      variants={variants}
    >

• Add utility functions decodeEncodedVariant and isOptionValueCombinationInEncodedVariant for parsing product.encodedVariantExistence and product.encodedVariantAvailability fields. (#​2425) by @​lhoffbeck

• [Breaking change] (#​2572) by @​wizardlyhel

  Update all cart mutation methods from createCartHandler to return cart warnings.

  As of API version 2024-10, inventory errors about stock levels will no longer be included in the userErrors of cart mutations. Inventory errors will now be available in a new return field warnings and will contain explicit code values of MERCHANDISE_NOT_ENOUGH_STOCK or MERCHANDISE_OUT_OF_STOCK. Reference: https://shopify.dev/changelog/cart-warnings-in-storefront-api-cart

• Updated dependencies [8c89f298, 84a66b1e, 76cd4f9b]:

  • @​shopify/hydrogen-react@2024.10.0

v2024.7.10

Compare Source

Patch Changes

• This version adds support for the new cookie system in Shopify (_shopify_analytics and _shopify_marketing http-only cookies). It is backward compatible and still supports the deprecated _shopify_y and _shopify_s cookies. (#​3355) by @​kdaviduik

  • createRequestHandler can now be used for every Hydrogen app, not only the ones deployed to Oxygen. It is now exported from @shopify/hydrogen.
  • A new Storefront API proxy is now available in Hydrogen's createRequestHandler. This will be used to obtain http-only cookies from Storefront API. In general, it should be transparent but it can be disabled with the proxyStandardRoutes option.
  • Analytics.Provider component and useCustomerPrivacy hook now make a request internally to the mentioned proxy to obtain cookies in the storefront domain.

• Fixed a number of issues related to irregular behaviors between Privacy Banner and Hydrogen's analytics events. (#​3355) by @​kdaviduik

• Updated dependencies [c64e8e25]:

  • @​shopify/hydrogen-react@2024.7.7

v2024.7.9

Compare Source

v2024.7.8

Compare Source

v2024.7.7

Compare Source

v2024.7.6

Compare Source

v2024.7.5

Compare Source

v2024.7.4

Compare Source

v2024.7.3

Compare Source

v2024.7.2

Compare Source

v2024.7.1

Compare Source

v2024.4.7

Compare Source

v2024.4.6

Compare Source

v2024.4.5

Compare Source

v2024.4.4

Compare Source

v2024.4.3

Compare Source

v2024.4.2

Compare Source

v2024.4.1

Compare Source

v2024.4.0

Compare Source

v2024.1.6

[Compare Source](https://redirect.github.c

❗ Important

✂ PR body was truncated to here.