@contentful/optimization-node 1.1.0 → 1.2.0

package/README.md

@@ -1,6 +1,6 @@
 <p align="center">
   <a href="https://www.contentful.com/developers/docs/personalization/">
-    <img alt="Contentful Logo" title="Contentful" src="https://raw.githubusercontent.com/contentful/optimization/optimization-node-v1.1.0/contentful-icon.png" width="150">
+    <img alt="Contentful Logo" title="Contentful" src="https://raw.githubusercontent.com/contentful/optimization/optimization-node-v1.2.0/contentful-icon.png" width="150">
   </a>
 </p>
 
@@ -11,12 +11,12 @@
 <div align="center">
 
 [Guides](https://contentful.github.io/optimization/documents/Documentation.Guides.html) ·
-[Reference](https://contentful.github.io/optimization) · [Contributing](https://github.com/contentful/optimization/blob/optimization-node-v1.1.0/CONTRIBUTING.md)
+[Reference](https://contentful.github.io/optimization) · [Contributing](https://github.com/contentful/optimization/blob/optimization-node-v1.2.0/CONTRIBUTING.md)
 
 </div>
 
 The Optimization Node SDK implements stateless server-side optimization behavior on top of the
-[Optimization Core SDK](https://github.com/contentful/optimization/blob/optimization-node-v1.1.0/packages/universal/core-sdk/README.md). Use it for server rendering, server
+[Optimization Core SDK](https://github.com/contentful/optimization/blob/optimization-node-v1.2.0/packages/universal/core-sdk/README.md). Use it for server rendering, server
 functions, and Node services that need request-scoped profile evaluation or event emission.
 
 If you are integrating a Node application, start with [Getting Started](#getting-started), then use
@@ -104,7 +104,7 @@ are part of the same application.
 
 The Node SDK is stateless. It does not maintain consent, profile, or browser persistence state
 between requests. For cross-SDK consent guidance, see
-[Consent management in the Optimization SDK Suite](https://github.com/contentful/optimization/blob/optimization-node-v1.1.0/documentation/concepts/consent-management-in-the-optimization-sdk-suite.md).
+[Consent management in the Optimization SDK Suite](https://github.com/contentful/optimization/blob/optimization-node-v1.2.0/documentation/concepts/consent-management-in-the-optimization-sdk-suite.md).
 
 | Option              | Required? | Default                | Description                                                 |
 | ------------------- | --------- | ---------------------- | ----------------------------------------------------------- |
@@ -222,10 +222,10 @@ to `forRequest()`.
 
 ### Content resolution
 
-When a `contentful.js` client is available, prefer SDK-managed fetching by entry ID. Configure the
-client once, then call `fetchOptimizedEntry()` on a request-bound client after an accepted
-Experience API call. `forRequest()` clients use the latest selected optimizations when omitted;
-singleton calls require explicit `selectedOptimizations`.
+When a `contentful.js` client is available, prefer SDK-managed fetching by entry ID or content type
+and slug. Configure the client once, then call `fetchOptimizedEntry()` on a request-bound client
+after an accepted Experience API call. `forRequest()` clients use the latest selected optimizations
+when omitted; singleton calls require explicit `selectedOptimizations`.
 
 ```ts
 const optimization = new ContentfulOptimization({
@@ -237,12 +237,19 @@ const optimization = new ContentfulOptimization({
 
 const requestOptimization = optimization.forRequest({ consent: true, profile })
 await requestOptimization.page()
-const { baselineEntry, entry } = await requestOptimization.fetchOptimizedEntry('hero-entry')
+const { baselineEntry, entry } = await requestOptimization.fetchOptimizedEntry({
+  contentType: 'productPage',
+  slug: req.params.slug,
+  entryQuery: { locale: appLocale },
+})
 ```
 
 Use `fetchContentfulEntries()` or `prefetchManagedEntries()` when a route knows several managed
-entry IDs. Entries with the same normalized query share one `getEntries()` call; same-tick
-single-entry calls can join that batch. Large `getEntries()` fetches are split into 100-ID chunks.
+entry sources. A slug source accepts `slugField` when the content model does not use the default
+`slug` field. Slug lookup enforces its content-type, field selector, and two-result uniqueness limit
+after merging `entryQuery`; successful resolution uses the fetched entry's `sys.id`. Slug handoffs
+nest the normalized descriptor under `managedEntry` and retain that ID in `entryId`. Equivalent ID
+sources retain same-query batching and 100-ID chunking.
 
 If your application already fetched the baseline entry, keep using the manual resolver:
 
@@ -308,9 +315,9 @@ package directory.
   step-by-step server-side integration guide
 - [Node SDK generated reference](https://contentful.github.io/optimization/modules/_contentful_optimization-node.html) -
   exported API reference
-- [Node reference implementation](https://github.com/contentful/optimization/blob/optimization-node-v1.1.0/implementations/node-sdk/README.md) - server-rendered
+- [Node reference implementation](https://github.com/contentful/optimization/blob/optimization-node-v1.2.0/implementations/node-sdk/README.md) - server-rendered
   implementation using request-scoped SDK calls
-- [Node + Web reference implementation](https://github.com/contentful/optimization/blob/optimization-node-v1.1.0/implementations/node-sdk+web-sdk/README.md) -
+- [Node + Web reference implementation](https://github.com/contentful/optimization/blob/optimization-node-v1.2.0/implementations/node-sdk+web-sdk/README.md) -
   hybrid SSR and browser implementation
-- [Optimization Web SDK](https://github.com/contentful/optimization/blob/optimization-node-v1.1.0/packages/web/web-sdk/README.md) - browser SDK used when the same application
+- [Optimization Web SDK](https://github.com/contentful/optimization/blob/optimization-node-v1.2.0/packages/web/web-sdk/README.md) - browser SDK used when the same application
   also needs client-side consent, persistence, tracking, or live updates

package/dist/260.mjs

@@ -1,4 +1,4 @@
-const OPTIMIZATION_NODE_SDK_VERSION = "1.1.0";
+const OPTIMIZATION_NODE_SDK_VERSION = "1.2.0";
 const OPTIMIZATION_NODE_SDK_NAME = "@contentful/optimization-node";
 export { ANONYMOUS_ID_COOKIE, ANONYMOUS_ID_KEY } from "@contentful/optimization-core/constants";
 export { OPTIMIZATION_NODE_SDK_NAME, OPTIMIZATION_NODE_SDK_VERSION };

package/dist/constants.cjs

@@ -30,7 +30,7 @@ __webpack_require__.d(__webpack_exports__, {
     OPTIMIZATION_NODE_SDK_VERSION: ()=>OPTIMIZATION_NODE_SDK_VERSION
 });
 const constants_namespaceObject = require("@contentful/optimization-core/constants");
-const OPTIMIZATION_NODE_SDK_VERSION = "1.1.0";
+const OPTIMIZATION_NODE_SDK_VERSION = "1.2.0";
 const OPTIMIZATION_NODE_SDK_NAME = "@contentful/optimization-node";
 exports.ANONYMOUS_ID_COOKIE = __webpack_exports__.ANONYMOUS_ID_COOKIE;
 exports.ANONYMOUS_ID_KEY = __webpack_exports__.ANONYMOUS_ID_KEY;

package/dist/index.cjs

@@ -6,7 +6,7 @@ var __webpack_modules__ = {
             OPTIMIZATION_NODE_SDK_VERSION: ()=>OPTIMIZATION_NODE_SDK_VERSION
         });
         require("@contentful/optimization-core/constants");
-        const OPTIMIZATION_NODE_SDK_VERSION = "1.1.0";
+        const OPTIMIZATION_NODE_SDK_VERSION = "1.2.0";
         const OPTIMIZATION_NODE_SDK_NAME = "@contentful/optimization-node";
     }
 };

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@contentful/optimization-node",
   "description": "Node.js SDK for Contentful Optimization",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "license": "MIT",
   "repository": {
     "type": "git",
@@ -88,6 +88,6 @@
     }
   },
   "dependencies": {
-    "@contentful/optimization-core": "1.1.0"
+    "@contentful/optimization-core": "1.2.0"
   }
 }