I believe the import paths should be aliased now that more components for the extension are communicating with one another i.e, the Data Editor and DFDL Runtime interaction.
I have a working example for the data editor extension that allows importing subdirectories within the data editor source as: import * as clientPanel from '@dataEditor/panel' or import { activate } from '@dataEditor/activation'. The most beneficial would be the components that utilize the MessageCommand from the data editor extension side.
I believe the import paths should be aliased now that more components for the extension are communicating with one another i.e, the Data Editor and DFDL Runtime interaction.
I have a working example for the data editor extension that allows importing subdirectories within the data editor source as:
import * as clientPanel from '@dataEditor/panel'orimport { activate } from '@dataEditor/activation'. The most beneficial would be the components that utilize theMessageCommandfrom the data editor extension side.