Load 3.0 codepen examples in documentation once more

[wegry]

Reasons for making this change

The React module's Component property wasn't defined in the 3.0 UMD bundle for some reason in codepen. Use ESM @rjsf/core bundle instead.

fixes #2447

Checklist

• I'm updating documentation
  • I've checked the rendering of the Markdown text I've added
  
• I'm adding or updating code
  • I've added and/or updated tests
  • I've updated docs if needed
• I'm adding a new feature
  • I've updated the playground with an example use of the feature

[epicfaace]

Thanks for fixing this. But does this mean that the UMD bundle no longer works? Is there a potential fix for that issue as well?

[wegry]

@epicfaace I don't know. I haven't used UMD consciously in years if ESM is available. I'd expect if UMD was broken, it'd get raised as an issue otherwise.

[wegry]

Alright, looks like the external change I had made to the webpack.config.js was assuming the UMD bundle would be used from a bundler/module aware system. It did not account for React/ReactDOM being an ambient global (like the non-esm CDN approach).

Tested with a local build and https://gist.github.com/wegry/d17568136713cd9bf697aca624acfe3e

[epicfaace]

Great, thanks for finding the fix! :)

[wegry]

I don't think this plugin is usable within a library. I'm almost certain that we're just incurring a build time cost with no usable change in output.

It makes sense for it to be available within the playground and docs though.

[epicfaace]

Yeah, that's right. Perhaps we could split it so it's only available for the playground and docs in a separate PR though?