ThemeProvider divergence between @theme-ui/core and theme-ui

Describe the bug Implementation of ThemeProvider is inconsistent depending on what package you pull it from. theme-ui looks to be re-exporting it from @theme-ui/theme-provider, while @theme-ui/core ships its own (simpler) implementation.

While @theme-ui/theme-provider is in-line with the documentation (BodyStyles, et al), blames suggest both have been updated in relatively recent past - so not sure which is the canonical implementation.

To Reproduce Steps to reproduce the behavior:

1. Check sources
2. Notice diverging implementations

(or alternatively, try to use the ThemeProvider from @theme-ui/core and notice it doesn’t touch the body styles).

Expected behavior Both packages implement the same behaviour

Screenshots N/A

Additional context N/A

[hasparus]

Thanks for the explanation, ackwell! Yup, I can see how it’s confusing now. Okay, I think we can do a few things

• Rename ThemeProvider in cover to ThemeUICoreProvider.
• Describe it in the docs. State the difference between the provider here and the provider in theme-ui.
• Write docs for @theme-ui/theme-provider? It can be used in a MDX+ThemeContext+ColorModes bundle without @theme-ui/components (included in theme-ui), so it could be documented.

[atanasster]

@ackwell good catch - is seems @theme-ui/theme-provider is just slightly newer (4 months) vs @theme-ui/core (5 months)

imho, we should keep @theme-ui/theme-provider, but since in both cases @hasparus has been involved maybe he has more information.