Skip to content
This repository has been archived by the owner on Feb 16, 2023. It is now read-only.

i118n - how to deal with it across multiple projects #1

Open
EvanBurbidge opened this issue Oct 2, 2018 · 2 comments
Open

i118n - how to deal with it across multiple projects #1

EvanBurbidge opened this issue Oct 2, 2018 · 2 comments
Assignees
@sv2
Labels
question Further information is requested

Comments

@EvanBurbidge
Copy link

In the majority of projects i've seen translations are handled from a single .json, yml file etc etc, how would you handle a global messages / translations object in a project like this?
@sv2 sv2 self-assigned this Oct 3, 2018
@sv2 sv2 added the question Further information is requested label Oct 3, 2018
@sv2
Copy link
Contributor

sv2 commented Oct 3, 2018

From the top of my head, I would place localization file into the common package - this way it can be used across all modules - frontend, backend ...

@EvanBurbidge
Copy link
Author

Suppose that would work, one more quick question if you don't mind, why don't you precompile each fe package e.g. each package is a vue cli app and your main app imports the dist of that app?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@sv2 sv2

Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sv2 @EvanBurbidge