SuiteCommerce 2022.1: IE 11 Dropped, Third-Party Library Upgrades, New SMT Areas

What Changed

IE 11 Support Removed

SuiteCommerce, SuiteCommerce MyAccount, and SuiteCommerce Advanced 2022.1.0+ no longer support Internet Explorer 11. Older SCA versions prior to 2022.1.0 retain IE 11 support, but anything on the 2022.1 codebase does not. IE 11 may introduce breaking changes on these sites.

Third-Party Library Updates

Several bundled libraries received version bumps. These are reflected in distro.json:

• gulp-sass: 4.1.0 → 5.0.0 — This is a breaking upgrade. gulp-sass 5.0.0 no longer bundles node-sass, so node-sass 7.0.0 has been added as a separate dependency.
• Handlebars: 4.5.3 → 4.7.7
• is-my-json-valid: 2.20.2 → 2.20.4
• TypeScript: 4.1.2 → 4.1.6
• underscore.js: 1.10.2 → 1.13.1 — Note that underscore 1.13 introduces ES module support and deprecates a handful of utility methods. Review your custom modules for any deprecated underscore calls.

New SMT Areas in Base Theme

Three new Site Management Tools areas were added to the Base Theme, giving content managers additional drag-and-drop zones:

• banner_caselist — Scope: all pages, Module: Case, Template: case_list.tpl (Support Cases page)
• banner_invoiceopenlist — Scope: all pages, Module: Invoice, Template: invoice_open_list.tpl (Invoices page)
• banner_myaccount_bottom — Scope: all pages, Module: MyAccountApplication, Template: myaccount_layout.tpl (My Account pages)

If you have a custom theme that overrides the Base Theme, these areas will not appear automatically; you will need to add the corresponding area markup to your custom templates.

Configuration Property Rename

The Shopping > Catalog property formerly labeled Enable new search API endpoints has been renamed to Enable Personalized Item Search API Endpoints. The underlying property ID remains isNewSearchApiEnabled. No functional change—just a label update in the SuiteCommerce Configuration record.

Node.js Requirement

The developer tools (Theme, Extension, and core SCA tools) continue to require Node.js 12.21.0. Other versions may work but are not officially supported.

What to Do

1. Stop supporting IE 11. Remove any IE-specific polyfills or shims from custom extensions. Update any customer-facing documentation that references IE 11 as a supported browser.
2. Audit custom Sass compilation. The jump from gulp-sass 4 to 5 changes the compiler interface. If you have custom Gulp tasks that interact with Sass compilation, verify they still work. The explicit addition of node-sass 7.0.0 means the Sass compiler is now a peer dependency—confirm it resolves correctly in your node_modules.
3. Check for deprecated underscore.js usage. Review custom modules for any underscore methods deprecated between 1.10 and 1.13 (e.g., changes to _.iteratee behavior). Run your extension test suites against the updated library.
4. Review Handlebars templates. Handlebars 4.7.7 includes security fixes and stricter prototype access controls. If any custom helpers rely on prototype chain access, they may break. Test template rendering after upgrading.
5. Add new SMT areas to custom themes. If you override Base Theme templates for the Case List, Invoice Open List, or My Account Layout, manually add the new banner_caselist, banner_invoiceopenlist, and banner_myaccount_bottom SMT area tags to your custom .tpl files so content managers can use them.
6. If migrating SCA to 2022.1, audit your codebase for any deprecated method calls in the libraries listed above before deploying the migration. Oracle specifically warns that deprecated methods must be removed prior to migration.