Can I control the order of plugin wrapRootElement?

[aaronadamsCA]

Scenario:

• Sentry provides an ErrorBoundary component.
• Theme UI provides a ThemeProvider component.
• I'd like ErrorBoundary to have access to ThemeProvider context, so I can use theming in ErrorBoundary.fallback.

I'm currently using gatsby-plugin-theme-ui, which uses wrapRootElement to add its ThemeProvider. As far as I can tell, this always occurs before my own wrapRootElement call, meaning my ErrorBoundary cannot access ThemeProvider's context, since it's inside the ErrorBoundary.

This has also made me realize the potential for larger risks when it comes to the order in which wrapRootElement is executed.

I can't seem to find any docs; is the order defined, and is it something I can control?

[aaronadamsCA]

Note: I know I can just load ThemeProvider within the fallback, or remove the plugin and load ThemeProvider myself. My larger concern here is to understand wrapRootElement ordering, especially among multiple plugins. 👍

[herecydev]

There's no granular control over ordering, however the order of plugins in your gatsby-config.js determines the order of execution, so try swapping stuff around until your happy.

Of course, you could run into issues if, for another API, you required another reorder.