Right know we concentrate all of our translations string in a single common.json file which was fine for the time being. But as the app keeps growing we're starting to get some size warnings from next:
@calcom/web:dev: Warning: data for page "/auth/login" is 174 kB which exceeds the threshold of 128 kB, this amount of data can reduce performance.
@calcom/web:dev: See more info here: https://nextjs.org/docs/messages/large-page-data
The main culprit being that we download the whole common.json file on each page.

We could create namespaces for specific routes and call then on the get props methods as described in the docs.
From SyncLinear.com | CAL-698
Right know we concentrate all of our translations string in a single
common.jsonfile which was fine for the time being. But as the app keeps growing we're starting to get some size warnings from next:The main culprit being that we download the whole
common.jsonfile on each page.We could create namespaces for specific routes and call then on the get props methods as described in the docs.
From SyncLinear.com | CAL-698