Fix React Compiler memoization error in I18nProvider

[Copilot]

CI failing on eslint-plugin-react-hooks@7.0.1's preserve-manual-memoization rule. The rule enforces correct dependencies in useMemo hooks and cannot be suppressed with eslint-disable comments.

Changes

• packages/i18n/src/provider.tsx: Added config to useMemo dependency array

The I18nProvider component was memoizing the i18n instance based only on externalInstance, ignoring config despite using it:

// Before: incorrect dependencies
const i18nInstance = useMemo(
  () => externalInstance || createI18n(config),
  [externalInstance], // eslint-disable-line react-hooks/exhaustive-deps
);

// After: correct dependencies
const i18nInstance = useMemo(
  () => externalInstance || createI18n(config),
  [externalInstance, config],
);

This ensures the i18n instance is recreated when config changes, and allows the React Compiler to optimize correctly.

Original prompt

引用: https://github.com/objectstack-ai/objectui/actions/runs/21827984712/job/62977961122#step:7:1

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
objectui	Ready	Preview, Comment	Feb 9, 2026 3:28pm
objectui-console	Ready	Preview, Comment	Feb 9, 2026 3:28pm
objectui-storybook	Ready	Preview, Comment	Feb 9, 2026 3:28pm

[Copilot]

Pull request overview

Fixes CI failure from eslint-plugin-react-hooks@7.0.1 (react-hooks/preserve-manual-memoization) by correcting useMemo dependencies in I18nProvider, aligning memoization with the values used to create the i18n instance.

Changes:

• Add config to the useMemo dependency array used to create/memoize the i18nInstance.
• Remove the prior eslint-disable suppression for hook dependencies.

[Copilot]

With config in the dependency array, any caller passing an inline object literal (e.g. the docs/examples use config={{ defaultLanguage: 'zh' }}) will cause this memo to invalidate on every render and repeatedly run createI18n(config) (which calls i18next.createInstance().init(...)). Consider documenting that config must be referentially stable (memoized) or restructuring the provider so it only recreates the instance when config values meaningfully change.

[Copilot]

Now that config can trigger a new i18nInstance, language state is still initialized only once from the initial instance. If config changes and a new instance is created, language/direction can become out of sync with the new instance until a languageChanged event fires (which may never happen). Consider syncing language when i18nInstance changes (e.g., set it to i18nInstance.language || 'en' on instance change).