`nest` does not work in production bundle

[max-ae]

I am facing the following issue: I have a common dictionary, and would like to reference some keys in smaller dictionaries. See attached code.

This works fine in vite dev server, however, does not work in the production bundle (vite build && vite preview) - the strings do not get rendered.

Common content:

import { type Dictionary, t } from "intlayer";

const commonContent = {
  content: {
    period: {
      daily: t({ de: "Täglich", en: "Daily" }),
      monthly: t({ de: "Monatlich", en: "Monthly" }),
      weekly: t({ de: "Wöchentlich", en: "Weekly" }),
    },
    startPage: t({ de: "Startseite", en: "Start Page" }),
    submit: t({ de: "Absenden", en: "Submit" }),
  },
  key: "common",
} satisfies Dictionary;

export default commonContent;

concrete content:

import { type Dictionary, nest, t } from "intlayer";

const dashboardContent = {
  content: {
      period: nest("common", "period"),
      submit: nest("common", "submit"),
    },
  },
  key: "dashboard",
} satisfies Dictionary;

export default dashboardContent;

usage:

  const dashboard = useIntlayer("dashboard");

What works is this, but this goes against the purpose of the nesting function

import { type Dictionary, nest, t } from "intlayer";
import commonContent from "../content/common.content";

const dashboardContent = {
  content: {
      period: commonContent.content.period,
      submit: commonContent.content.submit,
    },
  },
  key: "dashboard",
} satisfies Dictionary;

export default dashboardContent;

[aymericzip]

Hey @max-ae,

Thanks for reporting. You’re right, the bundle optimization purge the related dictionary.
I’ll add a note in the documentation, as I’m not sure I’ll be able to fix it in a reasonable timeframe

For now, I recommend using two useIntlayer hooks instead of nesting them

[max-ae]

is there any timeline on this? 😃

[aymericzip]

Hey @max-ae,

No sorry, I have no timeline to provide.

I had several tries and optimizing nest nodes will apply to add additional steps, which can considerably impact the build performance. That's says I will have to rethink the way we optimize the bundle. And it can be quite critical, so I keep exploring new solutions