Connect the extension to the ADW application - Connect the extension to the ADW application - Alfresco - Alfresco Digital Workspace - Alfresco/Alfresco-Digital-Workspace/6.0/Alfresco-Digital-Workspace/Develop/Build-extensions/Create-your-first-ADW-extension/Scaffolding/Connect-the-extension-to-the-ADW-application - 6.0 - 6.0

import { MyAdwCustomizationsModule } from '@myorg/my-adw-customizations';
   
   @NgModule({
     imports: [
       environment.plugins.aca_aos ? AosExtensionModule : [],
       environment.plugins.aca_about ? AcaAboutModule : [],
       environment.plugins.adw_governance ? RecordModule : [],
       environment.plugins.adw_aps1 ? ProcessServicesExtensionModule : [],
       environment.plugins.adw_content_services
         ? ContentServicesExtensionModule
         : [],
       environment.plugins.adw_office365
         ? MicrosoftOfficeOnlineIntegrationExtensionModule
         : [],
       environment.plugins.adw_analytics ? ContentEeAnalyticsModule : [],
       MyExtensionModule
     ],
       providers: [
         { provide: PACKAGE_JSON, useValue: packageJson },
         { provide: DEV_MODE_TOKEN, useValue: true },
       ],
     })
   export class AppExtensionsModule {}

This is not a blocker, and one solution is to create a tsconfig.json file alongside tsconfig.app.json with the following content:

{ "extends": "./tsconfig.app.json" }

This guarantees that the files are taken into account during the application build process.

{
     "input": "extensions/my-extension/descriptor",
     "output": "/assets/plugins",
     "glob": "*.json"
   },
   {
     "input": "extensions/my-extension/i18n",
     "output": "/assets/my-extension/i18n",
     "glob": "**/*"
   },
   {
     "input": "extensions/my-extension/assets",
     "output": "/assets/",
     "glob": "**/*"
   }

You may not need the entire configuration, but we'll add them once to cover more scenarios.