Using dynamic import in bundleSource made it possible to use bundleSource for one format and not entrain all the tooling for other formats, like Rollup for getExport and Babel for endoZipBase64. But, it broke the flow of type information. This change proposed by @michaelfig rectifies the internal and external types.
Security Considerations
None.
Scaling Considerations
None.
Documentation Considerations
None.
Testing Considerations
This PR does not adequately test the exported type signature.
It would pair well with a change that relies on the exported types.
Compatibility Considerations
None.
Upgrade Considerations
None.
[ ] Includes *BREAKING*: in the commit message with migration instructions for any breaking change.
Description
Using dynamic import in bundleSource made it possible to use
bundleSource
for one format and not entrain all the tooling for other formats, like Rollup forgetExport
and Babel forendoZipBase64
. But, it broke the flow of type information. This change proposed by @michaelfig rectifies the internal and external types.Security Considerations
None.
Scaling Considerations
None.
Documentation Considerations
None.
Testing Considerations
This PR does not adequately test the exported type signature. It would pair well with a change that relies on the exported types.
Compatibility Considerations
None.
Upgrade Considerations
None.
[ ] Includes*BREAKING*:
in the commit message with migration instructions for any breaking change.[ ] UpdatesNEWS.md
for user-facing changes.