Is there any particular reason for why the translation json files are in the public folder? #1851
-
|
What is the benefit of having the translation json files in |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
The reason is pretty straightforward – so we can download them on the client side if needed. This used less these days, as It used to be the case that incoming namespace dependencies needed to be managed manually in |
Beta Was this translation helpful? Give feedback.
-
When would such a scenario occur? I guess you're referring to this: But would it be completely okay to just leave the files out of the public folder since I don't think I'll need to download translations on the client side? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, of course. |
Beta Was this translation helpful? Give feedback.
The reason is pretty straightforward – so we can download them on the client side if needed. This used less these days, as
getStaticPropsandgetServerSidePropshandle the chunking/management of assets for us.It used to be the case that incoming namespace dependencies needed to be managed manually in
getInitialProps.