What's New in PageBuilder Engine
Discover the latest updates to Arc XP's PageBuilder Engine application.
PageBuilder Engine release matrix
The following table provides an overview of which versions of PageBuilder Engine are available.
Release | Status | Release Date (Production) | End of support | Requirements |
|---|---|---|---|---|
6.x | Sandbox | April 28, 2025 | to be announced | Node 20.x |
5.x | Production | November 27, 2023 | September 30, 2025 | Node 18.x NPM 7.x or 8.x |
4.x | Deprecated | May 11, 2023 | July 10, 2024 | Node 16.x NPM 6.x or 7.x |
Release dates
Sandbox - Monday, April 14, 2025
Production - Monday, April 28, 2025
Release summary
PageBuilder Engine 6.0 introduces support for the Node.js 20 runtime, which ensures compatibility with the latest technologies while enhancing performance and security. There are no other functional or breaking changes for PageBuilder Engine or Arc XP blocks for bundles already running on Engine 5.0.
To plan your migration to PageBuilder Engine 6.0, see Migration from PageBuilder Engine 5.x and 6.x.
Users affected
Developers
Action required
AWS Node 18 runtime support and PageBuilder Engine 5.0 will be deprecated on September 30, 2025. To continue deploying changes in Arc XP environments beyond this date, you must upgrade to Engine 6.0.
Release dates
Sandbox and Production - Monday, March 17, 2025
Release summary
We added improved handling for encoded SVGs.
The
pagebuilderURLmethod is now available for server-side renders in output-types.If you include styled components within the
outputType, the PageBuilder Editor preview now displays those styles correctly. Previously, those styles were excluded within Editor preview but appeared in the actual render (outside of PageBuilder Editor).Our PageBuilder Engine version policy will be enforced by March 31, 2025. After this date, only Engine 5.1.3 will be available for Deployments. Versions 5.0.5, 5.1.1, and 5.1.2 will become unavailable in Deployer.
[Extended] Engine 5.0.7 will become unavailable on April 10, 2025.
Users affected
Developers
Action required
Our PageBuilder Engine version policy will be enforced by March 31, 2025. After this date, only Engine 5.1.3 will be available for Deployments. Versions 5.0.5, 5.1.1, and 5.1.2 will become unavailable in Deployer.
Release dates
Sandbox - Monday, February 3, 2025
Production - Monday, March 3, 2025
(was previously Tuesday, February 18, 2025)
Release summary
Introducing Micro Experiences (MX), a new capability within PageBuilder designed to enhance flexibility and efficiency for development teams. MX allows you to create multiple independent PageBuilder instances, each configured with its own codebase and features. This empowers organizations to tailor digital experiences for specific business need or audience segments while maintaining operational efficiency.
Key Benefits
Parallel Deployments: Teams can work and deploy changes independently, improving collaboration and productivity.
Enhanced Efficiency: Streamline workflows to accelerate development and reduce time to market.
Minimized Risk: Isolate business-critical components to reduce the impact of deployment errors.
Use Cases
Launching new digital properties with tailored designs and functionality.
Isolating business-critical systems like subscriptions and identity management.
Supporting multiple development teams with independent environments.
Iterative redesigns or upgrades without disrupting existing systems.
Availability and Setup
MX is available as an opt-in feature for PageBuilder customers. To enable MX for your organization, contact Arc XP Customer Support.
Learn More
Users affected
Developers
Action required
None
Release dates
Sandbox - Tuesday, February 4, 2025
Production - Monday, February 10, 2025 (was previously February 4)
Release summary
We updated PageBuilder Engine to support Micro Experiences.
Users affected
Developers
Action required
None
Release dates
Sandbox and Production - Monday, December 16, 2024
Release summary
This hotfix reverses the styled-components dependency to 5.3.5 to keep the Engine release in a non-breaking path.
Users affected
Developers
Action required
None
Release dates
Sandbox - Thursday, December 5, 2024 (was previously Tuesday, December 3, 2024)
Production - Monday, December 16, 2024 (was previously Tuesday, December 10, 2024)
Release summary
Micro Experiences Support: Initial support for Micro Experiences has been added to PageBuilder Engine. (Details about the Micro Experience feature will be announced separately.)
Security Enhancements: Implemented key security updates and performed dependency upgrades to maintain system integrity and performance.
Bug Fixes: Resolved an issue in Engine 5.0.7 where multiple client-side API calls were being triggered unnecessarily.
Users affected
Developers
Action required
No action required, and customers can safely deploy their current Engine 5.0.x bundle (that's tested and deployed with Engine 5.1.0) with no additional work required.
Release dates
Sandbox - Thursday, August 22, 2024
Production - Monday, August 26, 2024
Release summary
SPA Context Update: Fixed an issue in the Single Page Application (SPA) where the context was not being updated correctly.
Enhanced Meta Tag Handling: The Editor UI now supports both the property and name fields for generating Meta tags, offering more flexibility in meta tag management.
Preparation for Upcoming Micro Experiences Feature: Implemented a new resolver payload validation and updated the logic of generating cache keys, to support each Micro Experience has its own isolated cache space.
Users affected
Developers
Action required
None
Release dates
Sandbox - Thursday, May 16, 2024
Production - Tuesday, May 21, 2024
Release summary
Fixed a bug in SPA navigation preventing the page from accessing the correct global content.
Added additional type-safety around Bandito integrations
Implemented support for disabling client side data such as globalContent and contentCache for a given output type. See Output Type API documentation to learn more.
Prevent devtool override from affecting production builds
Fixed a bug where custom content sources throwing HTTP 301 redirects was not working correctly.
Users affected
Developers
Action required
None
Release dates
Sandbox - Wednesday, April 24, 2024
Production - Monday, April 29, 2024
Release summary
Faster local builds
We've improved local build speed using parallel threads that can be enabled with using parallel: true in arc.config.json.
Support for larger, complex bundles
You can now use a new build flag to prevent duplicated node modules in compiled content sources, resulting in smaller final server-side bundles. This allows you to have more space for your dependencies or more complex codebases. This is an opt-in behavior controlled in arc.config.json using compiler.contentSources.excludeModules.
Bug fixes
Fixed a bug in layouts where renderable content was incorrectly reflecting the original on-load value and didn't update when adding or removing components from PageBuilder Editor.
Surfacing node module loading errors to users during compilation to help client developers troubleshoot errors caused by dependencies.
Users affected
Developers
Action required
None
Release dates
Sandbox - Monday, January 29, 2024
Production - Monday, February 5, 2024
Release summary
All React components now properly rehydrate. This issue was caused by the underlying JSX parsing code using the legacy hydration method, which had been deprecated and replaced in the current React version.
Support for
schemaNamein content-source configs is now restored. This resolves a potential issue where stringifying a content source might strip the schema-name field from its body.Type-safety of
fetchandresolvemethods in Content Sources is now improved to prevent errors that may occur.
Users affected
Developers
Action required
None
Release dates
Sandbox - Wednesday, January 3, 2024
Production - Monday, January 8, 2024
Release summary
We optimized the content source compilation for duplicate bundled modules, which creates reduced bundle size inside deployed AWS Lambda and provides the ability to deploy larger bundle code and dependencies.
The custom TTL functionality inside of the Fetch Content Sources is now restored.
A silent validation now exists on the developer-defined content-source configuration options and unexpected content types now use their default values. This resolves some potential bugs where, for example, the
transformproperty may be set tonulland cause the content-source to raise an HTTP 500 error when it is invoked. The new validation logic replaces thetransform: nullwith an identity function (transform: x => x). Consequently, the risk of undefined behavior arising from incorrectly defined-configuration options is now mitigated.Content sources now consistently apply default parameters across content source types.
Users affected
Developers
Action required
None
Release dates
Sandbox & Production - Monday, November 27, 2023
Release summary
This release fixes a bug in the content-source caching logic that could crash upstream APIs on large traffic pages. This bug was caused by a change that resulted in cache entries not updating if they already existed.
Users affected
Developers
Action required
Clients who want to upgrade to Engine 5.x can learn more in Migrating from PageBuilder Engine 4.x to 5.x.
Release dates
Sandbox - Monday, November 13, 2023
Production - Monday, November 27, 2023
Release summary
PageBuilder Engine 5.0 supports Node.js 18 runtime. Newer Node.js runtime is the only change compared to Engine 4 versions.
There is no other functionality, or breaking change on PageBuilder Engine and Arc XP Blocks usage for bundles already upgraded to Engine 4.
Upgrading
If you're upgrading from Engine 3, see Engine 3 to 4 migration guide for the changes between Engine 3 and 4.
If you're upgrading from 4 to 5, you should expect minimal to no change in your bundle code, except that your dependencies may require development effort to support the new Node.js 18 runtime.
With every major runtime change, dependencies you use in your bundle (npm packages) may have introduced their breaking behaviors with runtime upgrades. We advise to you to review your npm packages' project pages for breaking changes in these packages. They may have published guides for upgrading if it requires change in your implementation.
We have compiled these suggestions in a brief Migrating from PageBuilder Engine 4.x to 5.x guide.
Users affected
Developers
Action Required
Engine 3 and 4 will be deprecated on March 31, 2024. You must upgrade to Engine 5.0 to be able to deploy changes in Arc XP environments after this date.
See full release notes and Deprecation notice: PageBuilder Engine 3 and Engine 4 notice for more information.