Kiswendsida Kikone

congratulation on the release. I'm getting the following error when installing 5.0.0-beta.2: Module not found: Can't resolve '@rjsf/core/dist/components/fields/ArrayField' Apparently, the typescript types are generated but no js files

> u give me an expanded context on where you are seeing this error (in other words what is trying to import from that directory location)? All of the source...

> What are you hoping to do by importing `ArrayField`? Are you trying to override it or something? Yes. I have a use case where I override ArrayField when needed...

> > Yes. I have a use case where I override ArrayField when needed and just mount ArrayField when not needed. I think the component folder needs to be exposed....

The compomemt will fail at rendering "timeout" : 5000 ```json [{ "type": "error", "message": "Timeout: Unable to communicate with the parent App", "params": { "externalCommand": "userPreferences", "timeout": 5000 } },...

This is a weird situation I'm using react-json-tree 0.10.5 This is the message I'm getting :  My guess was that the valueGetter was not defined for node of type...

> @kikonejacob In 5.0.0-beta.7 we added a new field called `ArraySchemaField` (defaulting to `SchemaField`) which lets you override the way an array item `children` is rendered. This is the `children`...

I'm getting the error even with a freshly bootstrapped nx react library project ```error at error (/dev/projects/mynxtest/node_modules/rollup/dist/shared/rollup.js:198:30) at throwPluginError (/dev/projects/mynxtest/node_modules/rollup/dist/shared/rollup.js:21718:12) at Object.error (/dev/projects/mynxtest/node_modules/rollup/dist/shared/rollup.js:22672:20) at RollupContext.error (/dev/projects/mynxtest/node_modules/rollup-plugin-typescript2/dist/rollup-plugin-typescript2.cjs.js:1457:26) at /dev/projects/mynxtest/node_modules/rollup-plugin-typescript2/dist/rollup-plugin-typescript2.cjs.js:27639:26 at Array.forEach...

@AgentEnder I get the same type of error with create-nx-workspace@canary I can confirm that the bug was introduced on 18.2 , 18.1 works as expected. Steps to reproduce the error...

I tried the on('error') event but it only displays an error message. Parsing description to find out error is not sustainable as the message could change and sometimes the message...