Ant Design static message and Modal methods bypass ConfigProvider theme and locale context

Answer to the question

In Ant Design v5 the imperative helpers message, notification and Modal.confirm are rendered outside the normal React tree. As a result they do not consume any ConfigProvider context by default. The following properties are guaranteed to be ignored when using the static APIs:

• theme (token overrides)
• locale (language strings)
• prefixCls
• direction & rtl
• componentSize
• renderEmpty
• getPopupContainer
• getPrefixCls
• iconPrefixCls
• iconRender
• transitionName

These omissions are intentional and documented for backward compatibility; earlier major releases (v4) behaved the same.

Effect of App and useApp()

The App component internally wraps its children in a ConfigProvider and exposes the same context to the static helpers. When App is mounted, any subsequent calls to the static APIs will inherit:

• theme tokens (light/dark, custom token overrides)
• locale (translated message strings)

Other ConfigProvider props such as prefixCls or componentSize are still ignored by the static helpers, even inside App.

Recommended placement of App

To guarantee that imperative calls from nested components see the intended context, App must be an ancestor of the component that triggers the call. The minimal safe pattern is:

import { App } from 'antd';

ReactDOM.render(
  
    
  ,
  document.getElementById('root')
);

With this arrangement, message.success('OK'), notification.info({ message: 'Hi' }) and Modal.confirm({ title: 'Confirm' }) will all respect the current theme and locale. If a static call is executed before App mounts (e.g., during module initialization or in a server‑side render that omits App), the helpers will fall back to the default English text and light theme.

Verification steps

1. Wrap your app in App and set a dark theme and a non‑English locale via ConfigProvider.
2. From a nested component, trigger message.success('Success') and observe the dark background and translated text.
3. Remove the surrounding App wrapper, trigger the same call, and confirm that the default light theme and English message appear.

These steps confirm the documented behavior. If you are using Ant Design v4, the static helpers will always use the defaults; migration to App is required for context propagation.