۶Ƶ

Documentation

AEM Universal Editor does not support importmap “scopes” section

Last update: Fri Jul 11 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

When using ۶Ƶ Experience Manager as a Cloud Service (AEMaaCS) - Sites with Universal Editor, the scopes section of the importmap defined in the head.html file is automatically removed. This behavior disrupts design systems that depend on scoped JavaScript imports to load modules under specific paths. To resolve the issue, add JavaScript mappings under the imports section instead of using the scopes property.

Description description

Environment

۶Ƶ Experience Manager as a Cloud Service (AEMaaCS) - Sites (Development)

Issue/Symptoms

  • Universal Editor removes the scopes section from the importmap in head.html.
  • Scoped JavaScript imports fail to load, breaking design system functionality.
  • No configuration option exists to enable scopes support in Universal Editor.

Resolution resolution

Universal Editor currently supports only the imports section of the importmap and does not recognize or retain the scopes property. To work around the issue:

  1. Open your head.html file and locate the importmap definition.
  2. Move all scoped JavaScript mappings from the scopes section into the imports section.
  3. Ensure each required module is explicitly defined under imports with its full path. For example,
{  "imports": {    "@example/library/": "https://unpkg.com/@example/library@version/path/",    "@example/icons/": "https://unpkg.com/@example/icons@version/path/"  }}

If your implementation depends on scoped imports and cannot be restructured, contact ۶Ƶ Support with detailed use case information for further evaluation.

Universal Editor Introduction in the AEMaaCS user guide.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f