22.4.1

22.4.1

🐛 Bug Fixes

• [sitecore-jss-nextjs] Fix Chromes editing mode when rendering host URL is internally redirected in XMCloud (#2019)
• [templates/next.js] sitemap.xml endpoint returns 404 (#2023)

22.4.0

22.4.0

🐛 Bug Fixes

• [sitecore-jss-nextjs] Improve performance for redirect middleware. (#2003)
• [sitecore-jss-nextjs] Fix unnecessary escaping of valid regex operators in SXA rewrite patterns (#1999)
• [sitecore-jss] Fixed question marks not being handled correctly in escapeNonSpecialQuestionMarks method, when parsing regular expressions (#2014)
• [templates/nextjs-sxa] Fix font-awesome imports in custom workspaces. (#1998)
• [templates/nextjs] [templates/nextjs-sxa] Ensure DISABLE_SSG_FETCH variable is correctly handled in error pages(#2007)

🛠 Breaking Change

• [all packages] [all samples] Remove Axios (#2006) (#2008) (#2011)(#2013)(#2015)
  (#2016)
  • AxiosDataFetcher is replaced by the NativeDataFetcher.
  • AxiosDataFetcherConfig is replaced by NativeDataFetcherConfig.
  • AxiosResponse is replaced by NativeDataFetcherResponse.
  • NativeDataFetcherError: a new error type introduced for native data fetching operations.
  • Default fetcher i.e. NativeDataFetcher.fetch is of type NativeDataFetcherFunction<T> but can be overridden by custom fetcher using the existing HttpDataFetcher<T> type.
  • NativeDataFetcher now exposes fetch, get, post, delete, put, head methods.
  • NativedDataFetcher.fetch now accepts second parameter of type RequestInit instead of unknown.

22.3.0 / 22.3.1

22.3.0 / 22.3.1

🐛 Bug Fixes

• [templates/angular-xmcloud] Navigation component link forces full page reload (#1958)
• [sitecore-jss-nextjs] Link component prefetches files (#1956)
• [templates/nextjs] [templates/react] [templates/angular] [templates/vue] Fixed an issue when environment variable is undefined (not present in .env), that produced an "undefined" value in generated config file (#1875)
• [templates/nextjs] Fix embedded personalization not rendering correctly after navigation through router links. (#1911)
• [template/angular] Prevent client-side dictionary API call when SSR data is available (#1930) (#1932)
• [sitecore-jss-angular] Fix default empty field components to not render the unwanted wrapping tags (#1937) (#1940)
• [sitecore-jss-angular] Fix image field style property not rendered properly (#1944)
• [sitecore-jss-angular] Fix nested dynamic placeholders not being displayed in Pages (#1947)
• [sitecore-jss-dev-tools] getMetadata() now uses npm query command to get the list and exact versions of packages. this solution works for monorepo setups (#1949)
• [templates/nextjs-sxa] Fix an alignment issue where components using both me-auto and ms-md-auto classes resulted in inconsistent alignment of elements. (#1946) (#1950) (#1955)
• [sitecore-jss-proxy] [sitecore-jss-nextjs] Fix for getCSPHeader so that it returns proper value for the CSP header when JSS_ALLOWED_ORIGINS lists multiple origins delimited with comma. (#1972)
• [sitecore-jss-proxy] Support Editing Host protection by handling OPTIONS preflight requests (#1976)
• [templates/nextjs] Disable x-powered-by header

🎉 New Features & Improvements

• [Beta] Angular support for XM Cloud with SPA Proxy:
  • [create-sitecore-jss] Introduced "node-xmcloud-proxy" addon (#1863)
  • [create-sitecore-jss] [template/angular] [template/angular-sxp] [template/angular-xmcloud] Introduced "angular-sxp", "angular-xmcloud" addons (#1838)(#1845)(#1858)(#1865):
    • The Angular app should now be initialized by providing both templates (or using CLI prompts):
      • SXP-based: 'angular,angular-sxp'
      • XMCloud-based: 'angular,angular-xmcloud'
    • Rework Angular initializer to support XMCloud and SXP journeys;
    • Add SXA styles to xmcloud addon
  • [create-sitecore-jss] [template/angular] [template/angular-xmcloud] [template/node-xmcloud-proxy] Edge Proxy / Context Id support (#1875)(#1885)
  • [create-sitecore-jss] Rework Angular initializer to support XMCloud and SXP journeys (#1845)(#1858)(#1868)(#1881)(#1882)(#1931)
    • [create-sitecore-jss] Allow node-xmcloud-proxy app to be installed alongside Angular SPA application
    • proxyAppDestination arg can be passed into create-sitecore-jss command to define path for proxy to be installed in
  • [templates/angular] [templates/angular-xmcloud] [template/node-xmcloud-proxy] [sitecore-jss-proxy] Introduced /api/editing/config endpoint (#1903)
  • [templates/angular] [templates/angular-xmcloud] [template/node-xmcloud-proxy] [sitecore-jss-proxy] Introduced /api/editing/render endpoint (#1908)
  • [templates/angular-xmcloud] [template/node-xmcloud-proxy] Personalization support (#1964#1971#1973)
  • [create-sitecore-jss] [sitecore-jss-angular] [template/angular-xmcloud] Angular SXA components
    • Angular placeholder now supports SXA components (#1870)
    • Component styles (#1917)
    • Title component (#1904)
    • Richtext component (#1864)
    • Container component (#1872)
    • Angular SXA layout (#1873)(#1880)(#1890)(#1906)
    • RowSplitter component(#1901)
    • LinkList component(#1898)
    • ColumnSplitter (#1889)
    • PartialDesignDynamicPlaceholder component (#1902)
    • Promo component (#1897)
    • PageContent component (#1905)
    • Navigation component (#1894)
  • [sitecore-jss-angular] Placeholder component will now render metadata code blocks when in Metadata Edit mode (#1918)
  • [sitecore-jss] [sitecore-jss-angular] Default Placeholder Content for empty fields in editMode metadata - in edit mode metadata in Pages, angular package field directives will render default or custom placeholder content if the provided field is empty; (#1916)
    • custom placeholder content can be provided to field directives by passing the corresponding input:
    • scDateEmptyFieldEditingTemplate for scDate
    • scGenericLinkEmptyFieldEditingTemplate for scGenericLink
    • scImageEmptyFieldEditingTemplate for scImage
    • scLinkEmptyFieldEditingTemplate for scLink
    • scRichTextEmptyFieldEditingTemplate for scRichText
    • scRouterLinkEmptyFieldEditingTemplate for scRouterLink
    • scTextEmptyFieldEditingTemplate for scText
  • [sitecore-jss-angular] [templates/angular-xmcloud] Render clientScripts / clientData. The new sc-editing-scripts component is exposed from sitecore-jss-angular package and required to be rendered on the page to enable Metadata Edit mode. (#1924)(#1948)
  • [sitecore-jss-angular] [templates/angular-xmcloud] XM Cloud Forms support (#1951):
    • New "Form" component is introduced in the sitecore-jss-angular package.
    • The Form component is declared in the Angular sample app.
    • Introduced plugins technique for component factory generation.
  • [template/node-xmcloud-proxy] [sitecore-jss-proxy] Introduced /api/healthz endpoint (#1928)
  • [sitecore-jss] [sitecore-jss-angular] Render field metdata chromes in editMode metadata - in edit mode metadata in Pages, angular package field directives will render wrapping code elements with field metadata required for editing; (#1926)
  • [angular-xmcloud] [sitecore-jss-angular] Analytics and CloudSDK integration
    • [angular-xmcloud] Add CloudSDK initialization on client side (#1952)(#1957)(#1961)
    • [angular-xmcloud] [sitecore-jss-angular] Add CDP Page View component to Angular XM Cloud add-on (#1957)
  • [templates/angular] Update dependencies and proxy build path value to be unix style path to support xmcloud deployment and monorepo starter kit in xmcloud foundation head (#1977)
  • [templates/angular] [templates/angular-sxp] [templates/angular-xmcloud] Updates for Angular XMC sample to work well with local containers and spa-starters monorepo in xmcloud-foundation (#1983)
  • [sitecore-jss-angular] [templates/angular] Integrate CloudSDK events firing (#1984)(#1990)
• [sitecore-jss] GenericFieldValue model is updated to accept Date type (#1916)
• [templates/vue] [sitecore-jss-vue] Vue version has been updated to 3.5 (#1995(#1970))

🛠 Breaking Change

• [sitecore-jss] Set FETCH_WITH.REST to 'REST' instead of 'Rest' (#1927):
  • The FETCH_WITH.REST constant has been updated to 'REST' instead of 'Rest' t...

22.2.1

22.2.1

🐛 Bug Fixes

• [sitecore-jss-react] [templates/nextjs-xmcloud] [BYOC] Form's submission is failing (#1966):

  • Updated @sitecore-feaas/clientside to v0.5.19.
  • Updated @sitecore/components to v2.0.1.
  • Passed rendering data to FEAAS.ExternalComponent.

  Make sure to update the relevant dependencies to be able to use the latest fixes.

• [sitecore-jss-react] [templates/nextjs-xmcloud] Updated @sitecore-cloudsdk to v0.4.1 (#1966)

22.2.0

22.2.0

🛠 Breaking Change

• [templates/nextjs-xmcloud] CloudSDK dependencies have been updated to 0.4.0 (#1933)
• [templates/nextjs-xmcloud] @sitecore/components dependency has been updated to 2.0.0 (#1933)
• [templates/nextjs-xmcloud] lib/context import has been removed. Values from temp/config can be used instead. (#1933)
• [sitecore-jss-nextjs] Context import and @sitecore-jss/sitecore-jss-nextjs/context submodule have been removed. (#1933)
• [sitecore-jss-nextjs] update personalize-middleware for CloudSDK 0.4.0 - pass enablePersonalizeCookie to CloudSDK.addPersonalize() function (#1963)

22.1.4

22.1.4

🐛 Bug Fixes

• [sitecore-jss-nextjs] [sitecore-jss] Resolved an issue with Netlify where URL query parameters were being sorted, causing redirect failures. Added a method to generate all possible permutations of query parameters, ensuring proper matching with URL patterns regardless of their order. (#1935)
• [sitecore-jss-nextjs] Fixed an issue with language-based redirects, ensuring users are correctly redirected to the appropriate language-specific pages rather than defaulting to the primary language. (#1938)

🎉 New Features & Improvements

• [sitecore-jss-nextjs] Expose MiddlewareBase class and MiddlewareBaseConfig type (#1941)
• [react] [nextjs] [angular] [vue] CacheClient, CacheOptions, MemoryCacheClient classes can now be imported into the app through corresponding a framework package (#1954)

21.8.0

21.8.0

🛠 Breaking Changes

[sitecore-jss-angular] [sitecore-jss-schematics] [templates/angular] Upgrade Angular to v17 (#1939)

• Updated Angular and core dependencies to ~17.3.11
• Updated Typescript to ~5.2.2
• Updated import statements from zone.js/dist/zone-node to zone.js

22.1.3

22.1.3

🐛 Bug Fixes

• [sitecore-jss-nextjs] Addressed an issue where the x-middleware-rewrite header caused redirects to fail during execution on Netlify. (#1915)
• [sitecore-jss-nextjs] Fixed incorrect behavior of redirects on Netlify service. This fix does not resolve issues related to multilingual redirects. (#1919)

22.1.2

22.1.2

🐛 Bug Fixes

• [sitecore-jss-nextjs] [templates/nextjs] Update nextjs to 14.2.7 (#1911)
  • Make sure to update your app to use the latest Next.js version 14.2.7. It will fix the case when Embedded Personalization / A/B Testing is not executed after navigating through the router links
• [sitecore-jss] Fix isEditorActive returning false in XMCloud Pages (#1912)
• [templates/nextjs] [XM Cloud] FEAAS / BYOC Components are not visible on the page with running A/B test (#1914)
  • Make sure to update the PagePropsFactory plugins order, these plugins should be executed after the page-props-factory\plugins\personalize.ts plugin to ensure that personalized layout data is used:
    • page-props-factory/plugins/component-themes.ts
    • page-props-factory/plugins/component-props.ts
• [sitecore-jss-nextjs] Resolved an issue with redirects that was caused by the x-middleware-next header in Next.js. This header prevented the flow from being interrupted properly, resulting in redirects not functioning correctly in certain cases. (#1899)

22.1.1

22.1.1

🎉 New Features & Improvements

• [XM Cloud] [Metadata Mode] [Next.js] API was changed, next.js preview data provides a new parameter layoutKind therefore, please make the necessary updates in the app in plugins/preview-mode.ts as shown in the following PR to experience a smooth upgrade.
• [sitecore-jss] [sitecore-jss-nextjs] Pass sc_layoutKind to GraphQLEditingService request header to support shared/final editing layouts (#1907)
• [sitecore-jss] GraphQLRequestClient's request method now supports dynamic headers based on specific request (#1907)

  client.request(query, variables, { headers })