Only overwrite ns config if it provided

[NamPNQ]

Now we require including serverSideTranslation to every page that needed to translate

With this change, we can ignore that behavior by using all namespace available

Checklist

• only relevant code is changed (make a diff before you submit the PR)
• run tests npm run test
• tests are included
• commit message and code follows the Developer's Certification of Origin

Checklist (for documentation change)

• only relevant documentation part is changed (make a diff before you submit the PR)
• motivation/reason is provided
• commit message and code follows the Developer's Certification of Origin

[adrai]

I don't really understand what this should exactly change...
Maybe create a reproducible example?
Can you please provide a new test case that fails without that change and succeeds with this change?

[NamPNQ]

@adrai I just update my PR, can you take a look, I split this to every step for each commit, and add example
The example of auto-static-optimize is just copied from simple, modify config in _app, next-i18next.config and static page without getStaticProps

[adrai]

The tests are failing...
and I still don't get why ...(ns && { ns }) should change anything...
btw: I get this error with your example:

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/jest-environment-jsdom@29.7.0	Transitive: eval	+14	777 kB	simenb
npm/jest@29.7.0	Transitive: environment, eval, filesystem, network, shell, unsafe	+127	9.61 MB	simenb

🚮 Removed packages: npm/@types/react-dom@18.2.25, npm/eslint-config-next@14.0.4, npm/eslint-config-next@14.1.4, npm/http-server@14.1.1, npm/locize-cli@7.15.1, npm/next-language-detector@1.1.0, npm/next@14.0.4, npm/next@14.1.4

View full report↗︎

[NamPNQ]

@adrai
Replacing {ns} with {...(ns&&{ns}} was necessary due to server-side behavior, as evident in the code at https://github.com/i18next/next-i18next/blob/master/src/config/createConfig.ts#L254. When ns isn't provided, the server loads all namespaces. However, for auto static, ns isn't defined in the configuration, resulting in it being set to undefined. Consequently, no translations occur.

Currently, I'm not having any a solution for handling this mismatch. Since rendering occurs on the server side, while the client side lacks namespace information for preloading, translations won't occur, leading to a mismatch.

For test fail, because I'm missing add build:example for that

[adrai]

The mismatch is exactly because setversideTranslations is not called... so this will never work.

The mismatch needs to be resolved else I can't merge this PR.

[NamPNQ]

I update to use config ns and initImmediate: false to fix mismatch, the mismatch only happens in cache first time (the translation not fetched) or the cache expired

[adrai]

it's included in v15.3.0