fix(deps): update dependency @nacelle/storefront-sdk to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@nacelle/storefront-sdk (source)	^1.0.3 -> ^2.0.0
@nacelle/storefront-sdk (source)	^1.7.10 -> ^2.0.0
@nacelle/storefront-sdk (source)	^1.3.1 -> ^2.0.0
@nacelle/storefront-sdk (source)	^1.7.1 -> ^2.0.0
@nacelle/storefront-sdk (source)	^1.5.1 -> ^2.0.0
@nacelle/storefront-sdk (source)	^1.7.4 -> ^2.0.0
@nacelle/storefront-sdk (source)	^1.1.1 -> ^2.0.0
@nacelle/storefront-sdk (source)	^1.0.3 -> ^2.0.0

---

Release Notes

getnacelle/nacelle-js (@​nacelle/storefront-sdk)

v2.0.3

Compare Source

Patch Changes

• 6f2e5f1: Updated the default request retry logic to retry in response to all network errors. To customize request retry logic, you can provide your own configured instance of @urql/exchange-retry to the Storefront SDK's exchanges parameter.

v2.0.2

Compare Source

Patch Changes

• 254f5b0: Fixes an internal issue with @nacelle/storefront-sdk's build process, which was causing some external package code to be inadvertently bundled in the @nacelle/storefront-sdk package code. This issue both increased the package size and caused issues in Nuxt 2 projects.

v2.0.1

Compare Source

Patch Changes

• 9cdc2e2: Updates the Storefront SDK internals to rely on the most recent version of @urql/exchange-persisted. This should speed up the time it takes to install @nacelle/storefront-sdk, because we no longer have to patch @urql/exchange-persisted with patch-package.
• f3a05ca: Adds an x-nacelle-sdk-version header to all requests. This improves tracing and observability in the event of a support request.

v2.0.0

Compare Source

Major Changes

• 650c0ac: The Storefront SDK accepts a new fetchClient intialization parameter. You can use this to pass a custom fetch client to the Storefront SDK; it will be used in all Nacelle Storefront GraphQL requests.

  BREAKING: The Storefront SDK no longer accepts token, currencyCode, connector, debugMode, onDataError,subscriptionEndpoint, subscriptionToken, nor subscriptionSpaceId in the client initialization parameters. These properties are also no longer included in the return value of the getConfig method.

• 650c0ac: Adds an exchanges property to the Storefront SDK's initialization parameters. This new parameter allows Storefront SDK users to explicitly specify custom urql exchanges. All exchanges used by the Storefront SDK's urql client are now exported individually and as a pre-configured array of defaultExchanges. The setConfig parameter no longer allows APQ functionality to be changed on-the-fly. APQ can only be disabled by explicitly excluding the persistedFetchExchange in the exchanges array provided to the exchanges initialization parameter.

• 650c0ac: Generate TypeScript types from the Nacelle Storefront GraphQL schema.

• 650c0ac: BREAKING: Storefront SDK methods other than .query, .after, .getConfig and .setConfig are no longer included in @nacelle/storefront-sdk. Other methods from @nacelle/storefront-sdk@1.x such as .products, .content etc. will be provided by a Storefront SDK plugin.

• 650c0ac: Breaking change: advancedOptions and enableAPQ are removed from the StorefrontClientParams, and will be replaced with the ability for the SDK users to pass their own exchanges as params instead, including the @urql/exchange-persisted exchange which enables APQ. See urql documentation for more information about the persisted query exchange: https://formidable.com/open-source/urql/docs/advanced/persistence-and-uploads/

• 650c0ac: Improves the .query method.

  • Adds support for tagged template literals via the gql helper function
  • Adds support for TypedDocumentNodes for strongly typed queries/responses. More info on TypedDocumentNodes and how to use them.
  • Returns {data,error} so errors can be handled in code instead of throwing on errors. For users wanting to get the data directly and throw on response errors, can use an after method like this:

  sdkClient.after('query', (response) => {
  	if (response.error) {
  		throw new Error(response);
  	} else {
  		return response.data;
  	}
  });

• 650c0ac: Adds persisted query support for all queries. This sends all requests as hashed get requests to take advantage of server-side caching in Nacelle's v2 infrastructure.

Minor Changes

• 650c0ac: Exposes new withConfig type that plugin authors can take advantage of to get access to the getConfig method of the sdk.
• 650c0ac: The .after method offers callback deletion and an improved TypeScript experience. Callbacks can now be registered with a callbackId. To delete a callback, provide null as the callback value, along with the callbackId of the callback you'd like to delete. In TypeScript projects, the .after method's method argument provides autocomplete with all of the possible values. After specifying the method, the .after method's callback argument is aware of the type signature that's specific to the method of interest.
• 650c0ac: Adds a trace id to the error key in the response. This trace id should be included in any support requests.

Patch Changes

• 650c0ac: Updated the query method to always send variables to the Storefront GraphQL API as objects, even if they are supplied to the query method as a stringified object. This change circumvents issues related to using a combination of APQ and stringified variables in Nacelle's Storefront GraphQL.
• 650c0ac: Removed the Storefront function that initialized the Storefront SDK. Instead, the SDK is initialized by creating a new instance of the StorefrontClient class.
• 650c0ac: Updated the README to advertise features and link to the Nacelle docs
• 650c0ac: Refactored the after method to make it agnostic to the return types of methods defined by Storefront SDK plugins.
• 650c0ac: Fixes Storefront SDK type definition resolution in native ESM projects
• 650c0ac: Fixed an issue that prevented the Storefront SDK from entering preview mode when initializing the client with a previewToken.
• 650c0ac: Fixed a TypeScript issue that was creating an undesirable coupling between the Storefront SDK and Commerce Queries plugin.
• 650c0ac: Fixed an issue with header names that was preventing the Storefront SDK from entering preview mode.
• 650c0ac: Upgraded the package internals to use @urql/core major version 4. This removes the dependency on the graphql package.
• 74bbbaf: Patches the internals of @urql/exchange-persisted to prevent issues with large queries.

v1.8.0

Compare Source

v1.7.10

Compare Source

v1.7.9

Compare Source

v1.7.8

Compare Source

v1.7.7

Compare Source

v1.7.6

Compare Source

v1.7.5

Compare Source

v1.7.4

Compare Source

v1.7.3

Compare Source

v1.7.2

Compare Source

v1.7.1

Compare Source

v1.7.0

Compare Source

v1.6.0

Compare Source

v1.5.3

Compare Source

v1.5.2

Compare Source

v1.5.1

Compare Source

v1.5.0

Compare Source

v1.4.1

Compare Source

v1.4.0

Compare Source

v1.3.1

Compare Source

v1.3.0

Compare Source

v1.2.1

Compare Source

v1.2.0

Compare Source

v1.1.2

Compare Source

v1.1.1

Compare Source

v1.1.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nacelle-gatsby-reference-store	❌ Failed (Inspect)			Oct 19, 2023 6:41pm
nacelle-gatsby-starter	❌ Failed (Inspect)			Oct 19, 2023 6:41pm
nacelle-next-reference-store	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 19, 2023 6:41pm
nacelle-next-starter	❌ Failed (Inspect)			Oct 19, 2023 6:41pm
nacelle-nuxt-reference-store	❌ Failed (Inspect)			Oct 19, 2023 6:41pm
nacelle-nuxt-starter	❌ Failed (Inspect)			Oct 19, 2023 6:41pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 46e0309

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR