Generate dist/dynamic-modules.json for relevant packages

[vojtechszocs]

This PR modifies scripts/build-single-packages.js so that a dist/dynamic-modules.json file is generated for each package containing dynamic modules.

# yarn install && yarn build
$ find . -name dynamic-modules.json
./packages/react-core/dist/dynamic-modules.json
./packages/react-icons/dist/dynamic-modules.json
./packages/react-table/dist/dynamic-modules.json
./packages/react-templates/dist/dynamic-modules.json

We generate dynamic-modules.json files to make it easier for consuming projects to share specific PatternFly dynamic modules (instead of sharing the whole package indexes) via webpack module federation.

Each dynamic-modules.json file maps package index exports to their corresponding dynamic modules, for example:

// packages/react-core/dist/dynamic-modules.json
{
  "ASTERISK": "dist/dynamic/helpers/htmlConstants",
  "AboutModal": "dist/dynamic/components/AboutModal",
  "AboutModalProps": "dist/dynamic/components/AboutModal",
  "Accordion": "dist/dynamic/components/Accordion",
  "AccordionContent": "dist/dynamic/components/Accordion",
  "AccordionContentProps": "dist/dynamic/components/Accordion",
  "AccordionExpandableContentBody": "dist/dynamic/components/Accordion",
  "AccordionExpandableContentBodyProps": "dist/dynamic/components/Accordion",
  "AccordionItem": "dist/dynamic/components/Accordion",
  "AccordionItemProps": "dist/dynamic/components/Accordion",
  "AccordionProps": "dist/dynamic/components/Accordion",
  "AccordionToggle": "dist/dynamic/components/Accordion",
  "AccordionToggleProps": "dist/dynamic/components/Accordion",
  // ...
}

The algorithm that parses dynamic module information favors modules with most specific file paths, for example dist/dynamic/components/Wizard/hooks is favored over dist/dynamic/components/Wizard.

Dynamic modules nested under deprecated or next directories are ignored.

Note: this code was ported from openshift/console#13521

[patternfly-build]

Preview: https://patternfly-react-pr-10046.surge.sh

A11y report: https://patternfly-react-pr-10046-a11y.surge.sh

[Hyperkid123]

I am wondering if it would be preferred to get some of the compiler options from https://github.com/patternfly/patternfly-react/blob/main/packages/tsconfig.base.json#L9-L12

[vojtechszocs]

This code just parses the relevant info from package-specific build outputs, i.e. there is nothing emitted.

I've hardcoded the above TypeScript compiler option defaults to keep things simple and self-contained.

I see no problem with individual scripts defining their own options assuming they represent a separate build step, i.e. my understanding is that packages/tsconfig.base.json base config is mainly used for building the packages via Rollup.

I can try reusing some options from the base config as suggested, but it shouldn't have any impact on the generated dynamic-modules.json files.

[nicolethoen]

@vojtechszocs @Hyperkid123
I'm noticing here that the generated react-core/dist/dynamic-modules.json file is listing:

...
"Modal": "dist/dynamic/next/components/Modal",
"ModalBox": "dist/dynamic/components/Modal",
...

So i'm not sure this is accounting for next components correctly.

[Hyperkid123]

@vojtechszocs I think the next/deprecated modules should not be listed. There are conflicting names and the API difference will cause unexpected issues.

[vojtechszocs]

@Hyperkid123 @nicolethoen

You are right, module paths containing either "next" or "deprecated" should be excluded.

This issue also exists in OpenShift Console dynamic plugin SDK code (dynamic-module-parser.ts).

I'll update this PR as well as relevant Console code.

[vojtechszocs]

@nicolethoen PR updated, please have a look.

Dynamic modules nested under deprecated or next directories are ignored.