@scilliakovalenko/sitecore-jss - npm Package Versions

21.7.1

🐛 Bug Fixes

• [sitecore-jss-nextjs] [templates/nextjs-xmcloud] Updated @sitecore-cloudsdk/* dependencies to ^0.2.4

22.0.0

🛠 Breaking Changes

• [sitecore-jss] Switch to edge site query for XP and gets config sites + sxa sites (ignoring website) (#1772)
  • Previously introduced Boolean useSiteQuery switch for XMCloud users has been removed.
  • Search query usage has been removed.
  • If you have any non-nextjs sites they should filter them out in multisite config plugin
• [sitecore-jss-nextjs] [templates/nextjs-xmcloud] CloudSDK dependencies are updated to version ^0.3.0 (#1779)
  • Please ensure @sitecore-cloudsdk/events dependency is updated
• [sitecore-jss-nextjs] Deprecated exports have been removed (#1780):
  • sitecore-jss-nextjs no longer exports isEditorActive, resetEditorChormes, resolveUrl, handleEditorFastRefresh, getPublicUrl functions. Use sitecore-jss-nextjs/utils instead.
  • getFEAASLibraryStylesheetLinks function has been removed in favor of getComponentLibraryStylesheetLinks
• [sitecore-jss-react] [templates/react] Deprecated media prop is removed from Image component. Use field prop instead (#1780)(#1785).
• [templates/react] [templates/angular] [templates/vue] [templates/node-headless-ssr-experience-edge] [sitecore-jss-react] [sitecore-jss-nextjs] (#1783):
  • GraphQL-based services can now only be initialized with clientFactory parameter. Previously deprecated option of providing endpoint and apiKey has been removed
  • Removed deprecated defaultProps react component property
• [templates/nextjs] GraphQL-based services can now only be initialized with clientFactory parameter. Previously deprecated option of providing endpoint and apiKey has been removed (#1780).
• [templates/nextjs] [templates/react] [templates/vue] [templates/angular] Deprecated JSS_APP_NAME environment variable has been removed (#1780).

21.7.0

🎉 New Features & Improvements

• [sitecore-jss-angular] Enhance Placeholder component error handling (#1744)
  • Placeholder component supports failed event that is triggered when the component fails to render.
  • Handle error in the Placeholder component more gracefully by using an appropriate error JssCanActivateRedirectError type for redirects handling.
  • JssModule.forChild now accepts component or component map type as a parameter.
  • Fixed missing guard this context when calling canActivate guard
• [sitecore-jss] [templates/nextjs-xmcloud] Load the content styles for the RichText component (#1670)(#1683) (#1684) (#1693)
• [templates/react] [sitecore-jss-react] Replace package 'deep-equal' with 'fast-deep-equal'. No functionality change only performance improvement (#1719) (#1665)
• [templates/nextjs-xmcloud] [sitecore-jss] [sitecore-jss-nextjs] [sitecore-jss-react] Add support for loading appropriate stylesheets whenever a theme is applied to BYOC and SXA components by introducing new function getComponentLibraryStylesheetLinks, which replaces getFEAASLibraryStylesheetLinks (which has been marked as deprecated) (#1722)
• [templates/nextjs-xmcloud] [sitecore-jss-nextjs] Add protected endpoint which provides configuration information (the sitecore packages used by the app and all registered components) to be used to determine feature compatibility on Pages side. (#1724 #1734)
• [sitecore-jss-nextjs] [templates/nextjs] [BYOC] Component Builder integration endpoint (#1729)
• [sitecore-jss] [templates/nextjs-xmcloud] Enable site GraphQL query for mutlisite in XMCloud instead of default search one. Site query should take "Valid for environment" SXA site setting into account when returning site list. (#1739)
  • To enable this on your existing app, modify the \scripts\config\plugins\multisite.ts file and add "useSiteQuery: true" to GraphQLSiteInfoService constructor call
• [sitecore-jss-nextjs] Set secure, httpOnly, sameSite attributes to the sc_site cookie by default: (#1746)
• [sitecore-jss] GraphQL Client Retry Improvements:
  • Handle additional string error codes like ECONNRESET, ETIMEDOUT, EPROTO. Can configure more using DefaultRetryStrategy.
  • Retries has now been enabled by default with a default value of 3. It can be disabled by configuring it to 0.
  • [Retry-After] header now falls back to the default delay time when it comes out to be empty. (#1755) (#1759) (#1763)
• [sitecore-jss-nextjs] [templates/nextjs-xmcloud] Updated @sitecore-cloudsdk/* dependencies to ^0.2.3
• [templates/nextjs-xmcloud] Updated @sitecore/components to ^1.1.10

🐛 Bug Fixes

• [templates/nextjs] [templates/nextjs-styleguide] Modify all GraphQLRequestClient import statements so that it gets imported from the /graphql submodule (#1728)
• [templates/node-headless-ssr-proxy] [node-headless-ssr-proxy] Add sc_site qs parameter to Layout Service requests by default (#1660)
• [templates/nextjs-sxa] Fix Image component when there is using Banner variant which set property background-image when image is empty. (#1689) (#1692)
• [templates/nextjs-sxa] Fix feature show Grid column in Experience Editor. (#1704)
• [sitecore-jss-nextjs] [templates/nextjs-xmcloud] SDK initialization rejections are now correctly handled. Errors should no longer occur after getSDK() promises resolve when they shouldn't (for example, getting Events SDK in development environment) (#1712 #1715 #1716)
• [sitecore-jss-nextjs] Fix redirects middleware for working with absolute url where is using site language context (#1727) (#1737)
• [templates/nextjs-sxa] Fix base styles of SXA components. Remove conflicted styles of BasicSite template. (#1757)

🛠 Breaking Changes

• [sitecore-jss-nextjs] [templates/nextjs] Upgrade to Next 14 (#1720)(#1723)
  • Due to changes in peer dependencies, please ensure your app uses Next version 14

🧹 Chores

• Upgrade to Node.js 20.x (#1679)(#1681)
• [nextjs/template] Upgrade graphql-codegen packages to latest (#1711)

21.6.2

🐛 Bug Fixes

• [templates/nextjs] Whitelist additional hostname for feaas component images to use with Next.js Image Optimization API (#1735)

21.6.1

🐛 Bug Fixes

• [sitecore-jss-nextjs] Internal link in RichText is broken when nested tags are added (#1718)
• [sitecore-jss-nextjs] Remove custom loader function i.e. sitecoreLoader to enable NextImage to use built-in image optimization from vercel. Also add default image remotePatterns in next.config.js for whitelisting remote image hostnames (#1726) (#1732)

21.6.0

🎉 New Features & Improvements

• [templates/react] [templates/angular] [templates/vue] [templates/node-headless-ssr-proxy] [templates/node-headless-ssr-experience-edge] (#1647) (#1672) Switch from using JSS_APP_NAME to SITECORE_SITE_NAME - environment and config variables in React, Vue, Angular templates as well as ssr node proxy apps templates have been renamed.
• [templates/nextjs] [sitecore-jss-nextjs] [sitecore-jss] (#1640) (#1662)(#1661) (#1672) (#1675) (#1710) Sitecore Edge Platform and Context support:
  • Introducing the clientFactory property. This property can be utilized by GraphQL-based services, the previously used endpoint and apiKey properties are deprecated. The clientFactory serves as the central hub for executing GraphQL requests within the application.
  • New SITECORE_EDGE_CONTEXT_ID environment variable has been added.
  • The JSS_APP_NAME environment variable has been updated and is now referred to as SITECORE_SITE_NAME.
• [templates/nextjs] Enable client-only BYOC component imports. Client-only components can be imported through src/byoc/index.client.ts. Hybrid (server render with client hydration) components can be imported through src/byoc/index.hybrid.ts. BYOC scaffold logic is also moved from nextjs-sxa addon into base template (#1628#1636)
• [templates/nextjs] Import SitecoreForm component into sample nextjs app (#1628)
• [sitecore-jss-nextjs] (Vercel/Sitecore) Deployment Protection Bypass support for editing integration. (#1634)
• [sitecore-jss] Support for both 'published' and 'staged' revisions of FEAAS stylesheets/themes based on Sitecore Edge Platform and Context (#1644) (#1645) (#1666)
• [sitecore-jss-nextjs] The GraphQLRequestClient import from @sitecore-jss/sitecore-jss-nextjs is deprecated, use import from @sitecore-jss/sitecore-jss-nextjs/graphql submodule instead (#1650 #1648)
• [create-sitecore-jss] Introduced nextjs-xmcloud initializer template. This will include all base XM Cloud features, including Personalize, FEaaS, BYOC, Sitecore Edge Platform and Context support. (#1653) (#1657) (#1658)
• [sitecore-jss-nextjs] [templates/nextjs-xmcloud] Page state (preview, edit, normal) is available through shared context. This allows access to the state for integrations such as CloudSDK and FEAAS. (#1703)

🐛 Bug Fixes

• [templates/nextjs] [sitecore-jss-nextjs] Fix making a fetch to a nextjs api route in an editing environment, by adding additional variable publicUrl in runtime config (#1656)
• [templates/nextjs-multisite] Fix site info fetch errors (now skipped) on XM Cloud rendering/editing host builds. (#1649) (#1653)
• [templates/nextjs-xmcloud] Fix double registration of BYOC components (#1707) (#1709)

🛠 Breaking Changes

• [create-sitecore-jss] The nextjs-personalize initializer add-on template has been removed and is replaced by the nextjs-xmcloud initializer template. You can use the interactive prompts or the --xmcloud argument to include this template. (#1653)
• [templates/nextjs] [sitecore-jss-nextjs] CloudSDK Integration (#1652) (#1659):
  • Removed the following properties from PersonalizeMiddleware: getPointOfSale, clientKey, endpoint. You now need to provide sitecoreEdgeContextId as a replacement.
  • PersonalizeMiddleware has transitioned to utilizing the CloudSDK package, replacing the previous dependency on Engage.
  • Introduced Context class, that is used to initialize the application Context and shared Software Development Kits (SDKs). Accessible within the @sitecore-jss/sitecore-jss-nextjs/context submodule.
  • Point of Sale resolution is fully removed, now it's handled by Sitecore Edge Proxy
• [templates/nextjs] [sitecore-jss-nextjs] The behavior of getPublicUrl() function has been changed - empty string is now considered valid value for PUBLIC_URL environment variable and, if defined, PUBLIC_URL will take precedence over the Vercel/Netlify env variables; the values of these variables should be adjusted as needed; PUBLIC_URL is commented out by default in .env; (#1656);
• [templates/angular] [sitecore-jss-angular] Update Angular to version 16 (#1690) (#1697):
  • Updated Angular to ~16.2.10
  • Updated Typescript to ~4.9.5
  • @angular-eslint/ng-cli-compat eslint rules are deprecated. Use @angular-eslint/recommended rules instead.
  • outputPath is not needed in angular.json for the build target since we provide it via CLI.
  • Added more properties to server buld angular.json:
    • deleteOutputPath: false,
    • outputHashing: none To don't provide them via CLI.
  • Replaced deprecated --deploy-url with --base-href ng build option.
  • Output server build to dist instead of dist/server, in order to don't move artifacts to the root folder (JSS convention requires to keep all the server artifacts in the dist folder and have server.bundle.js file as an entrypoint)
  • TransferState, makeStateKey now imported from @angular/core instead of @angular/platform-browser.
  • BrowserModule.withServerTransition is deprecated, APP_ID is used instead.
  • Removed deprecated lib entryComponents property.
  • Exported ImageFieldValue and LinkFieldValue interfaces.
  • See more information about the upgrade in the Angular 16 Migration Guide

🧹 Chores

• Security vulnerability audit (#1685)
• Removed "npm" field from "engines" property (#1698)
• Removed "engines" field for templates (#1701)