chore(dependencies): Bump next-i18next from 16.0.4 to 16.0.7

[dependabot]

Bumps next-i18next from 16.0.4 to 16.0.7.

Release notes

Sourced from next-i18next's releases.

v16.0.7

• Pages Router: fix duplicate i18next in client bundles — v16 shipped the Pages Router as CJS-only, which forced bundlers to load i18next via its require condition (i18next/dist/cjs) while user code loaded it via the import condition (i18next/dist/esm), producing two copies of i18next in the same bundle. The Pages Router now builds dual ESM + CJS outputs, and the ./pages and ./pages/serverSideTranslations exports declare matching import/require conditions. The server-only filesystem branch of createConfig has been extracted into a separate serverSideConfig module (injected via hook by serverSideTranslations) so createConfig no longer pulls Node built-ins into client bundles. Note: appWithTranslation no longer re-runs the server-side validation/preload during SSR — that work happens once, up-front, inside serverSideTranslations (in practice a no-op since appWithTranslation uses the browser client with pre-loaded resources). #2342

v16.0.6

• Pages Router: reloadOnPrerender now actually reloads — the option was previously calling reloadResources() on the browser-side i18next instance returned by appWithTranslation (which has no FS backend and is often null during getStaticProps/getServerSideProps). It now reloads on the disk-backed node-side instance, scoped to exactly the locales × namespaces being shipped, so edits to locale files appear without restarting next dev. Gated behind NODE_ENV !== 'production' to keep custom HTTP/locize/chained backends from being refetched on every prerender call. #2123
• App Router: reloadOnPrerender is now wired up — previously declared in the config types but never consumed. Same dev-only semantics as Pages Router: refetches translations from the configured backend (default FS or use-provided custom backend) before each render in development, deduplicated across getT calls within a single render via React's cache(). No effect in production builds. Note: when using a dynamic import()-based resourceLoader, hot-reload is bundler-dependent and may stall after the first edit because Turbopack/Webpack cache resolved JSON modules across HMR cycles — see the README "Dev tip" for the dev/prod-split pattern that gives full hot-reload.

v16.0.5

• Pages Router: export missing types from next-i18next/pages — TFunction, I18n, WithTranslation, WithTranslationHocType, and UseTranslation types are now properly re-exported, matching the v15 API surface #2339

Changelog

Sourced from next-i18next's changelog.

16.0.7

• Pages Router: fix duplicate i18next in client bundles — v16 shipped the Pages Router as CJS-only, which forced bundlers to load i18next via its require condition (i18next/dist/cjs) while user code loaded it via the import condition (i18next/dist/esm), producing two copies of i18next in the same bundle. The Pages Router now builds dual ESM + CJS outputs, and the ./pages and ./pages/serverSideTranslations exports declare matching import/require conditions. The server-only filesystem branch of createConfig has been extracted into a separate serverSideConfig module (injected via hook by serverSideTranslations) so createConfig no longer pulls Node built-ins into client bundles. Note: appWithTranslation no longer re-runs the server-side validation/preload during SSR — that work happens once, up-front, inside serverSideTranslations (in practice a no-op since appWithTranslation uses the browser client with pre-loaded resources). #2342

16.0.6

• Pages Router: reloadOnPrerender now actually reloads — the option was previously calling reloadResources() on the browser-side i18next instance returned by appWithTranslation (which has no FS backend and is often null during getStaticProps/getServerSideProps). It now reloads on the disk-backed node-side instance, scoped to exactly the locales × namespaces being shipped, so edits to locale files appear without restarting next dev. Gated behind NODE_ENV !== 'production' to keep custom HTTP/locize/chained backends from being refetched on every prerender call. #2123
• App Router: reloadOnPrerender is now wired up — previously declared in the config types but never consumed. Same dev-only semantics as Pages Router: refetches translations from the configured backend (default FS or use-provided custom backend) before each render in development, deduplicated across getT calls within a single render via React's cache(). No effect in production builds. Note: when using a dynamic import()-based resourceLoader, hot-reload is bundler-dependent and may stall after the first edit because Turbopack/Webpack cache resolved JSON modules across HMR cycles — see the README "Dev tip" for the dev/prod-split pattern that gives full hot-reload.

16.0.5

• Pages Router: export missing types from next-i18next/pages — TFunction, I18n, WithTranslation, WithTranslationHocType, and UseTranslation types are now properly re-exported, matching the v15 API surface #2339

Commits

• bf1daa0 16.0.7
• 2aff620 fix duplicate i18next in Pages Router client bundles #2342
• 1e11acc Route mixed-routers footer locize CTA to /i18next
• 5437896 Add Locize advice section near the top of README
• 8e1327f 16.0.6
• a0ad04c fix reloadOnPrerender for both routers #2123
• 7ce84a0 Modernize locize.com URLs and refresh UTM tags
• a172946 chore: ignore .env*, *.pem, *.key in .gitignore
• 21615be readme fix #2340
• ac75d44 trigger vercel
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.