Relative imports can cause issues during builds.

[Hyperkid123]

Discussed in #1164

^{Originally posted by steverhoades October 31, 2021}
I'm curious if it was a design choice to not have these available from the base package.
e.g. I must explicitly import this from @data-driven-forms/react-form-renderer/use-form-api or @data-driven-forms/react-form-renderer/use-field-api respectively vs. import {useFieldAPi} from @data-driven-forms/react-form-renderer.

I only ask as I've spent the last hour or so debugging why my microapp wasn't playing nice with it's application shell. Turns out it was moving the dependencies from the microapp to the shell that broke as I didn't explicitly declare use-form-api and use-field-api as dependency externals.

[Hyperkid123]

We are missing the TS exports. Or rather we use an incorrect casing for functions/constants. There is an easy way to fix this. Don't generate the root index.d.ts and create it by hand. Not very elegant but easy. I am also going to try and come up with a generator, but it might be impossible because only functions have the name property to get the correct name.

[Hyperkid123]

🎉 This issue has been resolved in version 3.15.6 🎉

The release is available on

• react-form-renderer (@latest dist-tag)

• ant-component-mapper (@latest dist-tag)

• blueprint-component-mapper (@latest dist-tag)

• carbon-component-mapper (@latest dist-tag)

• mui-component-mapper (@latest dist-tag)

• pf4-component-mapper (@latest dist-tag)

• suir-component-mapper (@latest dist-tag)

Data-Driven-Forms.org!