1.3.0
🎉 New Features & Improvements
[nextjs][App Router] Add support for server components in Design Studio (#280)(#300)(#301)(#303)- additional react components to handle dynamic rendering of server components
- includes refactoring of existing Design Library functionality
- this is a breaking change for applications based on Next.js App Router (beta) template. Please refer to the detailed upgrade guide for further instructions
- separate server and client import-map generation (#293)(#299
[core]Provide information about rendering host as part of code extraction (#286)[template/next-app-router]Add component runtime information to prevent invalid client/server component operations in Sitecore Pages (#291)[cli]Create short flags for CLI commands (#298)
🐛 Bug Fixes
- Added package.json "exports" field to ensure correct ESM/CJS module resolution for submodule imports. Previously defaulted to CJS bundles even when ESM was available. (#296)
[core]NativeDataFetcher error does not include Error instance properties (name, message, stack) (#295)[template/next-app-router]Remove component-level data fetching in favor of Server Components (#282)[core]NativeFetcher response does not match actual returned data (#284)[nextjs]Add regex variable substitution for absolute and external URL redirects. (#287)[nextjs][template/next-app-router][template/nextjs]Geo based Personalization not possible in Content SDK Personalize Middleware. (#288)[nextjs][template/next-app-router][template/nextjs]Geo based Personalization not possible in Content SDK Personalize Middleware. (#290)[nextjs]Remove locale property assignments in redirects middleware for App Router compatibility. (#292)[nextjs]Next Link props unavailable when using Sitecore Link component (#294) (#296)[nextjs][template/next-app-router][template/nextjs]Fix middleware initialization errors in local container development (#297)(#302)