@intlayer/next-intl 9.5.1 → 9.5.2

package/dist/cjs/client/NextIntlClientProvider.cjs

@@ -20,7 +20,7 @@ const NextIntlClientProvider = ({ locale, children, messages: _messages, timeZon
 	const pathname = (0, next_navigation.usePathname)();
 	const mode = _intlayer_config_built.routing?.mode ?? "prefix-no-default";
 	const resolvedLocale = locale ?? (mode === "prefix-all" || mode === "prefix-no-default" ? (0, _intlayer_core_localization.getLocaleFromPath)(pathname) : void 0);
-	return /* @__PURE__ */ (0, react_jsx_runtime.jsx)(next_intlayer.IntlayerClientProvider, {
+	return /* @__PURE__ */ (0, react_jsx_runtime.jsx)(next_intlayer.IntlayerProvider, {
 		locale: resolvedLocale,
 		...rest,
 		children

package/dist/cjs/client/NextIntlClientProvider.cjs.map

@@ -1 +1 @@
-{"version":3,"file":"NextIntlClientProvider.cjs","names":["getAppLogger","colorize","CYAN","usePathname","routing","getLocaleFromPath","IntlayerClientProvider"],"sources":["../../../src/client/NextIntlClientProvider.tsx"],"sourcesContent":["'use client';\n\nimport { log, routing } from '@intlayer/config/built';\nimport { CYAN } from '@intlayer/config/colors';\nimport { colorize, getAppLogger } from '@intlayer/config/logger';\nimport { getLocaleFromPath } from '@intlayer/core/localization';\nimport type { LocalesValues } from '@intlayer/types/module_augmentation';\nimport { usePathname } from 'next/navigation';\nimport type { NextIntlClientProvider as _NextIntlClientProvider } from 'next-intl';\nimport { IntlayerClientProvider } from 'next-intlayer';\nimport type { ComponentProps } from 'react';\n\n/**\n * Drop-in for next-intl's `NextIntlClientProvider`.\n * `messages`, `timeZone`, and `now` are accepted for API compatibility\n * but have no effect — Intlayer uses its own compiled dictionaries.\n */\nexport const NextIntlClientProvider: typeof _NextIntlClientProvider = ({\n  locale,\n  children,\n  messages: _messages,\n  timeZone: _timeZone,\n  now: _now,\n  ...rest\n}) => {\n  if (\n    process.env.NODE_ENV === 'development' &&\n    typeof _messages !== 'undefined'\n  ) {\n    const appLogger = getAppLogger({ log });\n    appLogger(\n      `${colorize('NextIntlClientProvider', CYAN)} do not pass the messages prop with intlayer. Messages are loaded automatically under the hood for bundle optimization reason`\n    );\n  }\n\n  // next-intl drives the locale from the request: apps render\n  // `<NextIntlClientProvider>` without a `locale` prop and the server resolves it\n  // from the `[locale]` route segment. As a client component we cannot read the\n  // server request here, so when no explicit `locale` is given we derive it from\n  // the URL (the same `[locale]` segment) using Intlayer's routing config. This\n  // keeps `useLocale`, `Link` and the locale switcher in sync with the URL\n  // instead of falling back to the stored cookie / default locale.\n  //\n  // Only prefix-based routing carries the locale in the path. For `no-prefix` /\n  // `search-params` the path has no locale segment, so we leave `locale`\n  // undefined and let the provider resolve it from storage (cookie) — deriving\n  // from the path there would wrongly clobber the cookie with the default locale.\n  const pathname = usePathname();\n  const mode = routing?.mode ?? 'prefix-no-default';\n  const isPrefixMode = mode === 'prefix-all' || mode === 'prefix-no-default';\n  const resolvedLocale =\n    locale ?? (isPrefixMode ? getLocaleFromPath(pathname) : undefined);\n\n  // `key={resolvedLocale}` remounts the provider when the locale changes via\n  // navigation (next-intl switches locale by routing to a locale-prefixed path).\n  // This re-seeds the client locale context so client components re-render in\n  // the new language instead of keeping the previous one.\n  return (\n    <IntlayerClientProvider\n      key={String(resolvedLocale)}\n      locale={resolvedLocale}\n      {...rest}\n    >\n      {children}\n    </IntlayerClientProvider>\n  );\n};\n\n/**\n *\n */\nexport type NextIntlClientProviderProps = Omit<\n  ComponentProps<typeof _NextIntlClientProvider>,\n  'messages'\n> & {\n  /**\n   * @deprecated\n   * has no use case with intlayer. Messages are loaded automatically under the hood for bundle optimization reason\n   */\n  messages?: never;\n  /**\n   * locale\n   */\n  locale: LocalesValues;\n};\n"],"mappings":";;;;;;;;;;;;;;;;;AAiBA,MAAa,0BAA0D,EACrE,QACA,UACA,UAAU,WACV,UAAU,WACV,KAAK,MACL,GAAG,WACC;CACJ,IACE,QAAQ,IAAI,aAAa,iBACzB,OAAO,cAAc,aAGrB,IADkBA,sCAAa,EAAE,gCAAI,CAC7B,CAAC,CACP,OAAGC,kCAAS,0BAA0BC,4BAAI,EAAE,8HAC9C;CAeF,MAAM,eAAWC,6BAAY;CAC7B,MAAM,OAAOC,gCAAS,QAAQ;CAE9B,MAAM,iBACJ,WAFmB,SAAS,gBAAgB,SAAS,0BAE3BC,+CAAkB,QAAQ,IAAI;CAM1D,OACE,2CAACC,sCAAD;EAEE,QAAQ;EACR,GAAI;EAEH;CACqB,GALjB,OAAO,cAAc,CAKJ;AAE5B"}
+{"version":3,"file":"NextIntlClientProvider.cjs","names":["getAppLogger","colorize","CYAN","usePathname","routing","getLocaleFromPath","IntlayerProvider"],"sources":["../../../src/client/NextIntlClientProvider.tsx"],"sourcesContent":["'use client';\n\nimport { log, routing } from '@intlayer/config/built';\nimport { CYAN } from '@intlayer/config/colors';\nimport { colorize, getAppLogger } from '@intlayer/config/logger';\nimport { getLocaleFromPath } from '@intlayer/core/localization';\nimport type { LocalesValues } from '@intlayer/types/module_augmentation';\nimport { usePathname } from 'next/navigation';\nimport type { NextIntlClientProvider as _NextIntlClientProvider } from 'next-intl';\nimport { IntlayerProvider } from 'next-intlayer';\nimport type { ComponentProps } from 'react';\n\n/**\n * Drop-in for next-intl's `NextIntlClientProvider`.\n * `messages`, `timeZone`, and `now` are accepted for API compatibility\n * but have no effect — Intlayer uses its own compiled dictionaries.\n */\nexport const NextIntlClientProvider: typeof _NextIntlClientProvider = ({\n  locale,\n  children,\n  messages: _messages,\n  timeZone: _timeZone,\n  now: _now,\n  ...rest\n}) => {\n  if (\n    process.env.NODE_ENV === 'development' &&\n    typeof _messages !== 'undefined'\n  ) {\n    const appLogger = getAppLogger({ log });\n    appLogger(\n      `${colorize('NextIntlClientProvider', CYAN)} do not pass the messages prop with intlayer. Messages are loaded automatically under the hood for bundle optimization reason`\n    );\n  }\n\n  // next-intl drives the locale from the request: apps render\n  // `<NextIntlClientProvider>` without a `locale` prop and the server resolves it\n  // from the `[locale]` route segment. As a client component we cannot read the\n  // server request here, so when no explicit `locale` is given we derive it from\n  // the URL (the same `[locale]` segment) using Intlayer's routing config. This\n  // keeps `useLocale`, `Link` and the locale switcher in sync with the URL\n  // instead of falling back to the stored cookie / default locale.\n  //\n  // Only prefix-based routing carries the locale in the path. For `no-prefix` /\n  // `search-params` the path has no locale segment, so we leave `locale`\n  // undefined and let the provider resolve it from storage (cookie) — deriving\n  // from the path there would wrongly clobber the cookie with the default locale.\n  const pathname = usePathname();\n  const mode = routing?.mode ?? 'prefix-no-default';\n  const isPrefixMode = mode === 'prefix-all' || mode === 'prefix-no-default';\n  const resolvedLocale =\n    locale ?? (isPrefixMode ? getLocaleFromPath(pathname) : undefined);\n\n  // `key={resolvedLocale}` remounts the provider when the locale changes via\n  // navigation (next-intl switches locale by routing to a locale-prefixed path).\n  // This re-seeds the client locale context so client components re-render in\n  // the new language instead of keeping the previous one.\n  return (\n    <IntlayerProvider\n      key={String(resolvedLocale)}\n      locale={resolvedLocale}\n      {...rest}\n    >\n      {children}\n    </IntlayerProvider>\n  );\n};\n\n/**\n *\n */\nexport type NextIntlClientProviderProps = Omit<\n  ComponentProps<typeof _NextIntlClientProvider>,\n  'messages'\n> & {\n  /**\n   * @deprecated\n   * has no use case with intlayer. Messages are loaded automatically under the hood for bundle optimization reason\n   */\n  messages?: never;\n  /**\n   * locale\n   */\n  locale: LocalesValues;\n};\n"],"mappings":";;;;;;;;;;;;;;;;;AAiBA,MAAa,0BAA0D,EACrE,QACA,UACA,UAAU,WACV,UAAU,WACV,KAAK,MACL,GAAG,WACC;CACJ,IACE,QAAQ,IAAI,aAAa,iBACzB,OAAO,cAAc,aAGrB,IADkBA,sCAAa,EAAE,gCAAI,CAC7B,CAAC,CACP,OAAGC,kCAAS,0BAA0BC,4BAAI,EAAE,8HAC9C;CAeF,MAAM,eAAWC,6BAAY;CAC7B,MAAM,OAAOC,gCAAS,QAAQ;CAE9B,MAAM,iBACJ,WAFmB,SAAS,gBAAgB,SAAS,0BAE3BC,+CAAkB,QAAQ,IAAI;CAM1D,OACE,2CAACC,gCAAD;EAEE,QAAQ;EACR,GAAI;EAEH;CACe,GALX,OAAO,cAAc,CAKV;AAEtB"}

package/dist/cjs/warnUnsupported.cjs

@@ -0,0 +1,28 @@
+Object.defineProperty(exports, Symbol.toStringTag, { value: 'Module' });
+let _intlayer_config_built = require("@intlayer/config/built");
+let _intlayer_config_colors = require("@intlayer/config/colors");
+let _intlayer_config_logger = require("@intlayer/config/logger");
+
+//#region src/warnUnsupported.ts
+/**
+* Warns, in development only, that a `next-intl` API is a no-op under the
+* intlayer adapter.
+*
+* The `NODE_ENV` check is what keeps `@intlayer/config`'s logger and its ANSI
+* colour table — around 6 KB — out of production bundles: with the branch
+* folded away nothing references the imports any more and they are shaken out.
+* That only works while `process.env.NODE_ENV` survives this package's own
+* build and reaches the consuming app's bundler, which is why `tsdown.config.ts`
+* pins `platform: 'neutral'`.
+*
+* @param api - Name of the shimmed `next-intl` export, e.g. `getMessages`.
+* @param reason - What the developer should do instead.
+*/
+const warnUnsupported = (api, reason) => {
+	if (process.env.NODE_ENV !== "development") return;
+	(0, _intlayer_config_logger.getAppLogger)({ log: _intlayer_config_built.log })(`${(0, _intlayer_config_logger.colorize)(api, _intlayer_config_colors.CYAN)} ${reason}`);
+};
+
+//#endregion
+exports.warnUnsupported = warnUnsupported;
+//# sourceMappingURL=warnUnsupported.cjs.map

package/dist/cjs/warnUnsupported.cjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"warnUnsupported.cjs","names":["colorize","CYAN"],"sources":["../../src/warnUnsupported.ts"],"sourcesContent":["import { log } from '@intlayer/config/built';\nimport { CYAN } from '@intlayer/config/colors';\nimport { colorize, getAppLogger } from '@intlayer/config/logger';\n\n/**\n * Warns, in development only, that a `next-intl` API is a no-op under the\n * intlayer adapter.\n *\n * The `NODE_ENV` check is what keeps `@intlayer/config`'s logger and its ANSI\n * colour table — around 6 KB — out of production bundles: with the branch\n * folded away nothing references the imports any more and they are shaken out.\n * That only works while `process.env.NODE_ENV` survives this package's own\n * build and reaches the consuming app's bundler, which is why `tsdown.config.ts`\n * pins `platform: 'neutral'`.\n *\n * @param api - Name of the shimmed `next-intl` export, e.g. `getMessages`.\n * @param reason - What the developer should do instead.\n */\nexport const warnUnsupported = (api: string, reason: string): void => {\n  if (process.env.NODE_ENV !== 'development') return;\n\n  getAppLogger({ log })(`${colorize(api, CYAN)} ${reason}`);\n};\n"],"mappings":";;;;;;;;;;;;;;;;;;;;AAkBA,MAAa,mBAAmB,KAAa,WAAyB;CACpE,IAAI,QAAQ,IAAI,aAAa,eAAe;CAE5C,0CAAa,EAAE,gCAAI,CAAC,CAAC,CAAC,OAAGA,kCAAS,KAAKC,4BAAI,EAAE,GAAG,QAAQ;AAC1D"}

package/dist/esm/client/NextIntlClientProvider.mjs

@@ -1,7 +1,7 @@
 'use client';
 
 import { log, routing } from "@intlayer/config/built";
-import { IntlayerClientProvider } from "next-intlayer";
+import { IntlayerProvider } from "next-intlayer";
 import { CYAN } from "@intlayer/config/colors";
 import { colorize, getAppLogger } from "@intlayer/config/logger";
 import { getLocaleFromPath } from "@intlayer/core/localization";
@@ -19,7 +19,7 @@ const NextIntlClientProvider = ({ locale, children, messages: _messages, timeZon
 	const pathname = usePathname();
 	const mode = routing?.mode ?? "prefix-no-default";
 	const resolvedLocale = locale ?? (mode === "prefix-all" || mode === "prefix-no-default" ? getLocaleFromPath(pathname) : void 0);
-	return /* @__PURE__ */ jsx(IntlayerClientProvider, {
+	return /* @__PURE__ */ jsx(IntlayerProvider, {
 		locale: resolvedLocale,
 		...rest,
 		children

package/dist/esm/client/NextIntlClientProvider.mjs.map

@@ -1 +1 @@
-{"version":3,"file":"NextIntlClientProvider.mjs","names":[],"sources":["../../../src/client/NextIntlClientProvider.tsx"],"sourcesContent":["'use client';\n\nimport { log, routing } from '@intlayer/config/built';\nimport { CYAN } from '@intlayer/config/colors';\nimport { colorize, getAppLogger } from '@intlayer/config/logger';\nimport { getLocaleFromPath } from '@intlayer/core/localization';\nimport type { LocalesValues } from '@intlayer/types/module_augmentation';\nimport { usePathname } from 'next/navigation';\nimport type { NextIntlClientProvider as _NextIntlClientProvider } from 'next-intl';\nimport { IntlayerClientProvider } from 'next-intlayer';\nimport type { ComponentProps } from 'react';\n\n/**\n * Drop-in for next-intl's `NextIntlClientProvider`.\n * `messages`, `timeZone`, and `now` are accepted for API compatibility\n * but have no effect — Intlayer uses its own compiled dictionaries.\n */\nexport const NextIntlClientProvider: typeof _NextIntlClientProvider = ({\n  locale,\n  children,\n  messages: _messages,\n  timeZone: _timeZone,\n  now: _now,\n  ...rest\n}) => {\n  if (\n    process.env.NODE_ENV === 'development' &&\n    typeof _messages !== 'undefined'\n  ) {\n    const appLogger = getAppLogger({ log });\n    appLogger(\n      `${colorize('NextIntlClientProvider', CYAN)} do not pass the messages prop with intlayer. Messages are loaded automatically under the hood for bundle optimization reason`\n    );\n  }\n\n  // next-intl drives the locale from the request: apps render\n  // `<NextIntlClientProvider>` without a `locale` prop and the server resolves it\n  // from the `[locale]` route segment. As a client component we cannot read the\n  // server request here, so when no explicit `locale` is given we derive it from\n  // the URL (the same `[locale]` segment) using Intlayer's routing config. This\n  // keeps `useLocale`, `Link` and the locale switcher in sync with the URL\n  // instead of falling back to the stored cookie / default locale.\n  //\n  // Only prefix-based routing carries the locale in the path. For `no-prefix` /\n  // `search-params` the path has no locale segment, so we leave `locale`\n  // undefined and let the provider resolve it from storage (cookie) — deriving\n  // from the path there would wrongly clobber the cookie with the default locale.\n  const pathname = usePathname();\n  const mode = routing?.mode ?? 'prefix-no-default';\n  const isPrefixMode = mode === 'prefix-all' || mode === 'prefix-no-default';\n  const resolvedLocale =\n    locale ?? (isPrefixMode ? getLocaleFromPath(pathname) : undefined);\n\n  // `key={resolvedLocale}` remounts the provider when the locale changes via\n  // navigation (next-intl switches locale by routing to a locale-prefixed path).\n  // This re-seeds the client locale context so client components re-render in\n  // the new language instead of keeping the previous one.\n  return (\n    <IntlayerClientProvider\n      key={String(resolvedLocale)}\n      locale={resolvedLocale}\n      {...rest}\n    >\n      {children}\n    </IntlayerClientProvider>\n  );\n};\n\n/**\n *\n */\nexport type NextIntlClientProviderProps = Omit<\n  ComponentProps<typeof _NextIntlClientProvider>,\n  'messages'\n> & {\n  /**\n   * @deprecated\n   * has no use case with intlayer. Messages are loaded automatically under the hood for bundle optimization reason\n   */\n  messages?: never;\n  /**\n   * locale\n   */\n  locale: LocalesValues;\n};\n"],"mappings":";;;;;;;;;;;;;;;;AAiBA,MAAa,0BAA0D,EACrE,QACA,UACA,UAAU,WACV,UAAU,WACV,KAAK,MACL,GAAG,WACC;CACJ,IAEE,OAAO,cAAc,aAGrB,AADkB,aAAa,EAAE,IAAI,CAC7B,CAAC,CACP,GAAG,SAAS,0BAA0B,IAAI,EAAE,8HAC9C;CAeF,MAAM,WAAW,YAAY;CAC7B,MAAM,OAAO,SAAS,QAAQ;CAE9B,MAAM,iBACJ,WAFmB,SAAS,gBAAgB,SAAS,sBAE3B,kBAAkB,QAAQ,IAAI;CAM1D,OACE,oBAAC,wBAAD;EAEE,QAAQ;EACR,GAAI;EAEH;CACqB,GALjB,OAAO,cAAc,CAKJ;AAE5B"}
+{"version":3,"file":"NextIntlClientProvider.mjs","names":[],"sources":["../../../src/client/NextIntlClientProvider.tsx"],"sourcesContent":["'use client';\n\nimport { log, routing } from '@intlayer/config/built';\nimport { CYAN } from '@intlayer/config/colors';\nimport { colorize, getAppLogger } from '@intlayer/config/logger';\nimport { getLocaleFromPath } from '@intlayer/core/localization';\nimport type { LocalesValues } from '@intlayer/types/module_augmentation';\nimport { usePathname } from 'next/navigation';\nimport type { NextIntlClientProvider as _NextIntlClientProvider } from 'next-intl';\nimport { IntlayerProvider } from 'next-intlayer';\nimport type { ComponentProps } from 'react';\n\n/**\n * Drop-in for next-intl's `NextIntlClientProvider`.\n * `messages`, `timeZone`, and `now` are accepted for API compatibility\n * but have no effect — Intlayer uses its own compiled dictionaries.\n */\nexport const NextIntlClientProvider: typeof _NextIntlClientProvider = ({\n  locale,\n  children,\n  messages: _messages,\n  timeZone: _timeZone,\n  now: _now,\n  ...rest\n}) => {\n  if (\n    process.env.NODE_ENV === 'development' &&\n    typeof _messages !== 'undefined'\n  ) {\n    const appLogger = getAppLogger({ log });\n    appLogger(\n      `${colorize('NextIntlClientProvider', CYAN)} do not pass the messages prop with intlayer. Messages are loaded automatically under the hood for bundle optimization reason`\n    );\n  }\n\n  // next-intl drives the locale from the request: apps render\n  // `<NextIntlClientProvider>` without a `locale` prop and the server resolves it\n  // from the `[locale]` route segment. As a client component we cannot read the\n  // server request here, so when no explicit `locale` is given we derive it from\n  // the URL (the same `[locale]` segment) using Intlayer's routing config. This\n  // keeps `useLocale`, `Link` and the locale switcher in sync with the URL\n  // instead of falling back to the stored cookie / default locale.\n  //\n  // Only prefix-based routing carries the locale in the path. For `no-prefix` /\n  // `search-params` the path has no locale segment, so we leave `locale`\n  // undefined and let the provider resolve it from storage (cookie) — deriving\n  // from the path there would wrongly clobber the cookie with the default locale.\n  const pathname = usePathname();\n  const mode = routing?.mode ?? 'prefix-no-default';\n  const isPrefixMode = mode === 'prefix-all' || mode === 'prefix-no-default';\n  const resolvedLocale =\n    locale ?? (isPrefixMode ? getLocaleFromPath(pathname) : undefined);\n\n  // `key={resolvedLocale}` remounts the provider when the locale changes via\n  // navigation (next-intl switches locale by routing to a locale-prefixed path).\n  // This re-seeds the client locale context so client components re-render in\n  // the new language instead of keeping the previous one.\n  return (\n    <IntlayerProvider\n      key={String(resolvedLocale)}\n      locale={resolvedLocale}\n      {...rest}\n    >\n      {children}\n    </IntlayerProvider>\n  );\n};\n\n/**\n *\n */\nexport type NextIntlClientProviderProps = Omit<\n  ComponentProps<typeof _NextIntlClientProvider>,\n  'messages'\n> & {\n  /**\n   * @deprecated\n   * has no use case with intlayer. Messages are loaded automatically under the hood for bundle optimization reason\n   */\n  messages?: never;\n  /**\n   * locale\n   */\n  locale: LocalesValues;\n};\n"],"mappings":";;;;;;;;;;;;;;;;AAiBA,MAAa,0BAA0D,EACrE,QACA,UACA,UAAU,WACV,UAAU,WACV,KAAK,MACL,GAAG,WACC;CACJ,IAEE,OAAO,cAAc,aAGrB,AADkB,aAAa,EAAE,IAAI,CAC7B,CAAC,CACP,GAAG,SAAS,0BAA0B,IAAI,EAAE,8HAC9C;CAeF,MAAM,WAAW,YAAY;CAC7B,MAAM,OAAO,SAAS,QAAQ;CAE9B,MAAM,iBACJ,WAFmB,SAAS,gBAAgB,SAAS,sBAE3B,kBAAkB,QAAQ,IAAI;CAM1D,OACE,oBAAC,kBAAD;EAEE,QAAQ;EACR,GAAI;EAEH;CACe,GALX,OAAO,cAAc,CAKV;AAEtB"}

package/dist/esm/warnUnsupported.mjs

@@ -0,0 +1,27 @@
+import { log } from "@intlayer/config/built";
+import { CYAN } from "@intlayer/config/colors";
+import { colorize, getAppLogger } from "@intlayer/config/logger";
+
+//#region src/warnUnsupported.ts
+/**
+* Warns, in development only, that a `next-intl` API is a no-op under the
+* intlayer adapter.
+*
+* The `NODE_ENV` check is what keeps `@intlayer/config`'s logger and its ANSI
+* colour table — around 6 KB — out of production bundles: with the branch
+* folded away nothing references the imports any more and they are shaken out.
+* That only works while `process.env.NODE_ENV` survives this package's own
+* build and reaches the consuming app's bundler, which is why `tsdown.config.ts`
+* pins `platform: 'neutral'`.
+*
+* @param api - Name of the shimmed `next-intl` export, e.g. `getMessages`.
+* @param reason - What the developer should do instead.
+*/
+const warnUnsupported = (api, reason) => {
+	if (process.env.NODE_ENV !== "development") return;
+	getAppLogger({ log })(`${colorize(api, CYAN)} ${reason}`);
+};
+
+//#endregion
+export { warnUnsupported };
+//# sourceMappingURL=warnUnsupported.mjs.map

package/dist/esm/warnUnsupported.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"warnUnsupported.mjs","names":[],"sources":["../../src/warnUnsupported.ts"],"sourcesContent":["import { log } from '@intlayer/config/built';\nimport { CYAN } from '@intlayer/config/colors';\nimport { colorize, getAppLogger } from '@intlayer/config/logger';\n\n/**\n * Warns, in development only, that a `next-intl` API is a no-op under the\n * intlayer adapter.\n *\n * The `NODE_ENV` check is what keeps `@intlayer/config`'s logger and its ANSI\n * colour table — around 6 KB — out of production bundles: with the branch\n * folded away nothing references the imports any more and they are shaken out.\n * That only works while `process.env.NODE_ENV` survives this package's own\n * build and reaches the consuming app's bundler, which is why `tsdown.config.ts`\n * pins `platform: 'neutral'`.\n *\n * @param api - Name of the shimmed `next-intl` export, e.g. `getMessages`.\n * @param reason - What the developer should do instead.\n */\nexport const warnUnsupported = (api: string, reason: string): void => {\n  if (process.env.NODE_ENV !== 'development') return;\n\n  getAppLogger({ log })(`${colorize(api, CYAN)} ${reason}`);\n};\n"],"mappings":";;;;;;;;;;;;;;;;;;;AAkBA,MAAa,mBAAmB,KAAa,WAAyB;CACpE,IAAI,QAAQ,IAAI,aAAa,eAAe;CAE5C,aAAa,EAAE,IAAI,CAAC,CAAC,CAAC,GAAG,SAAS,KAAK,IAAI,EAAE,GAAG,QAAQ;AAC1D"}

package/dist/types/warnUnsupported.d.ts

@@ -0,0 +1,18 @@
+//#region src/warnUnsupported.d.ts
+/**
+ * Warns, in development only, that a `next-intl` API is a no-op under the
+ * intlayer adapter.
+ *
+ * The `NODE_ENV` check is what keeps `@intlayer/config`'s logger and its ANSI
+ * colour table — around 6 KB — out of production bundles: with the branch
+ * folded away nothing references the imports any more and they are shaken out.
+ * That only works while `process.env.NODE_ENV` survives this package's own
+ * build and reaches the consuming app's bundler, which is why `tsdown.config.ts`
+ * pins `platform: 'neutral'`.
+ *
+ * @param api - Name of the shimmed `next-intl` export, e.g. `getMessages`.
+ * @param reason - What the developer should do instead.
+ */
+export declare const warnUnsupported: (api: string, reason: string) => void;
+//#endregion
+//# sourceMappingURL=warnUnsupported.d.ts.map

package/dist/types/warnUnsupported.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"warnUnsupported.d.ts","names":[],"sources":["../../src/warnUnsupported.ts"],"mappings":";;;;;;;;;;;;;;;qBAkBa,kBAAe,aAAe"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@intlayer/next-intl",
-  "version": "9.5.1",
+  "version": "9.5.2",
   "private": false,
   "description": "next-intl API adapter for intlayer — useTranslations, useLocale, getTranslations, getLocale, NextIntlClientProvider backed by next-intlayer",
   "keywords": [
@@ -111,18 +111,18 @@
     "typecheck": "tsc --noEmit --project tsconfig.types.json"
   },
   "dependencies": {
-    "@intlayer/config": "9.5.1",
-    "@intlayer/core": "9.5.1",
-    "@intlayer/dictionaries-entry": "9.5.1",
-    "@intlayer/engine": "9.5.1",
-    "@intlayer/types": "9.5.1",
-    "@intlayer/use-intl": "9.5.1",
-    "next-intlayer": "9.5.1",
-    "react-intlayer": "9.5.1"
+    "@intlayer/config": "9.5.2",
+    "@intlayer/core": "9.5.2",
+    "@intlayer/dictionaries-entry": "9.5.2",
+    "@intlayer/engine": "9.5.2",
+    "@intlayer/types": "9.5.2",
+    "@intlayer/use-intl": "9.5.2",
+    "next-intlayer": "9.5.2",
+    "react-intlayer": "9.5.2"
   },
   "devDependencies": {
-    "@types/node": "26.5.0",
-    "@types/react": "19.2.18",
+    "@types/node": "^22",
+    "@types/react": "19.3.0",
     "@utils/ts-config": "1.0.4",
     "@utils/ts-config-types": "1.0.4",
     "@utils/tsdown-config": "1.0.4",