The published @performant-software/core-data package initializes i18next with debug: true — it's visible as debug: !0 in dist/index.es112.js. Every consumer gets i18next's full ~50-line initialized {…} config dump plus languageChanged lines on the console; an FDS dev-server boot prints it three times (once in the TinaCMS process, twice in Astro).
It's the single largest block of noise in core-data-places dev logs. Flipping it to false (or gating it on an env var for library development) removes it everywhere downstream.
For comparison, @performant-software/shared-components already ships debug: false.
The published
@performant-software/core-datapackage initializes i18next withdebug: true— it's visible asdebug: !0indist/index.es112.js. Every consumer gets i18next's full ~50-lineinitialized {…}config dump pluslanguageChangedlines on the console; an FDS dev-server boot prints it three times (once in the TinaCMS process, twice in Astro).It's the single largest block of noise in core-data-places dev logs. Flipping it to
false(or gating it on an env var for library development) removes it everywhere downstream.For comparison,
@performant-software/shared-componentsalready shipsdebug: false.