@shopkit/data-layer 1.4.3 → 1.4.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.js CHANGED
@@ -3807,7 +3807,31 @@ var ProductService2 = class extends BaseCustomService {
3807
3807
  PRODUCT_ENDPOINTS.getProducts(options?.version),
3808
3808
  "POST",
3809
3809
  requestParams,
3810
- options
3810
+ {
3811
+ ...options || {},
3812
+ // A list read cannot know which products come back before it runs, so it
3813
+ // takes the broad `products` tag — the one place a broad tag is the correct
3814
+ // answer rather than a blunt one. Per-product reads deliberately omit it
3815
+ // (see getProduct), which is what keeps `revalidateTag("products")` from
3816
+ // becoming a catalog-wide PDP purge: it lands only on the surfaces that
3817
+ // actually render a list — sitemaps, search endpoints, PLP rails.
3818
+ //
3819
+ // This is the producer that tag had been missing. Merchant inventory routes
3820
+ // have been calling `revalidateTag("products")` all along, against nothing:
3821
+ // no read attached it, so those deliveries returned 200 having invalidated
3822
+ // nothing. Same failure the removed `search.reindex` event had, mirrored to
3823
+ // the producer side.
3824
+ //
3825
+ // No `search` tag on a query-bearing read: it would be attached only
3826
+ // alongside `products` and purged only alongside `products`, so it could
3827
+ // never invalidate anything `products` did not already reach. See the note
3828
+ // on CACHE_INVALIDATION_TYPES in @shopkit/webhooks — a tag with no
3829
+ // independent effect is the same dead weight as one with no producer.
3830
+ next: {
3831
+ ...options?.next || {},
3832
+ tags: [cacheTags.CacheTags.products(), ...options?.next?.tags || []]
3833
+ }
3834
+ }
3811
3835
  );
3812
3836
  if (!result || !result.products) {
3813
3837
  return formatResponse({
@@ -4163,9 +4187,12 @@ var ProductService2 = class extends BaseCustomService {
4163
4187
  }
4164
4188
  const payload = {
4165
4189
  storeId: this.config.storeId,
4166
- available: params.filters?.[0]?.available ?? true,
4167
4190
  collectionHandles: handles
4168
4191
  };
4192
+ const availability = params.filters?.[0]?.available;
4193
+ if (typeof availability === "boolean") {
4194
+ payload.available = availability;
4195
+ }
4169
4196
  if (params.filters && params.filters.length > 0) {
4170
4197
  const filter = params.filters[0];
4171
4198
  if (filter.price?.min !== void 0) {
@@ -4190,7 +4217,40 @@ var ProductService2 = class extends BaseCustomService {
4190
4217
  PRODUCT_ENDPOINTS.getCollectionsByHandles(options?.version),
4191
4218
  "POST",
4192
4219
  payload,
4193
- options
4220
+ {
4221
+ ...options || {},
4222
+ // The same tags the single-collection `getCollection` attaches, one set
4223
+ // per requested handle. This is the batch form of that read, so it has to
4224
+ // carry the same invalidation coverage: without it, moving a template from
4225
+ // COLLECTION to COLLECTION_BY_HANDLES silently opts the page out of
4226
+ // webhook invalidation, and it stays stale until its own `revalidate`
4227
+ // window elapses.
4228
+ //
4229
+ // Not hypothetical: home pages render their product grids through this
4230
+ // read, so `revalidateTag(collection:<handle>)` from a product.updated
4231
+ // webhook — which did purge that product's PDP and its collection page —
4232
+ // matched nothing on the home page, and an edited title sat there for the
4233
+ // rest of the ISR window.
4234
+ //
4235
+ // Same rationale and the same deliberate omission of `revalidate` as
4236
+ // getProductsByHandles above. Tagging a POST works: Next records a fetch's
4237
+ // tags on the enclosing page's cache entry before it decides whether the
4238
+ // response itself is cacheable.
4239
+ //
4240
+ // The type guard mirrors getProductsByHandles — CacheTags.collection()
4241
+ // calls .trim() on its argument and this array is widget-supplied, so a
4242
+ // stray null would throw and fail the whole read, not just one tag.
4243
+ next: {
4244
+ ...options?.next || {},
4245
+ tags: [
4246
+ cacheTags.CacheTags.collections(),
4247
+ ...handles.filter(
4248
+ (h) => typeof h === "string" && h.trim() !== ""
4249
+ ).map((h) => cacheTags.CacheTags.collection(h)),
4250
+ ...options?.next?.tags || []
4251
+ ]
4252
+ }
4253
+ }
4194
4254
  );
4195
4255
  if (!result || !result.collections) {
4196
4256
  return formatResponse({
@@ -4248,7 +4308,24 @@ var ProductService2 = class extends BaseCustomService {
4248
4308
  PRODUCT_ENDPOINTS.getCollectionFilters(options?.version, handle),
4249
4309
  "GET",
4250
4310
  void 0,
4251
- options
4311
+ {
4312
+ ...options || {},
4313
+ // Facets are derived from this collection's products — price range, brands,
4314
+ // availability — so anything that invalidates the collection invalidates its
4315
+ // filters. One tag, keyed on the same handle, means the existing
4316
+ // product.updated / collection.updated purges already cover them.
4317
+ //
4318
+ // No broad `collections` tag here, unlike getCollection: a filter set belongs
4319
+ // to exactly one collection, and bulk collection events already purge every
4320
+ // affected handle individually.
4321
+ next: {
4322
+ ...options?.next || {},
4323
+ tags: [
4324
+ cacheTags.CacheTags.collection(handle),
4325
+ ...options?.next?.tags || []
4326
+ ]
4327
+ }
4328
+ }
4252
4329
  );
4253
4330
  if (!result) {
4254
4331
  return formatResponse({