Option `include` with same named locale files should be merged about bundle-tools HOT 10 OPEN

anything that will provide possobility to split code and dont use translations directly in components is welcomed, at least this:
also the warning about local and global scope is very annoying

────locales
    │
    ├───en
    │   │   common.yaml
    │   │   component1.yaml
    │   │   component2.yaml
    │   
    ├───fr
    │   │   common.yaml
    │   │   component1.yaml
    │   │   component2.yaml

from bundle-tools.

Similar use-case. I'm trying to find a way to accomplish the folder structure below and use the folders as language key so messages can understand it. I thought about linking everything together in a src/i18n/index.ts but that is not supported either.

/src/i18n/
│   index.ts
│  
│
└───locales
    │
    ├───en-GB
    │   │   global.json
    │   │
    │   ├───components
    │   │       Example.json
    │   
    └───nl-NL
        │   global.json
        │
        ├───components
        │        Example.json

Then something like t('Example.key') or t('global.key') should be available.

I'm currently unable to use this plugin because this is a must the project I work in.

from bundle-tools.

This is a very needed feature if splitting code (and locales as well) into multiple modules or plugins.

from bundle-tools.

I've been digging into the code and found that the plugin is overriding resource paths, so only the last include is taken into account

Use instead

resourcePaths = [...resourcePaths, ...(await fg(inc))] ;

This doesn't fix the issue as the language is overriden after this array of language definitions, but I don't understand the code so good to be able to do a pull request

from bundle-tools.

This is a very needed feature if splitting code (and locales as well) into multiple modules or plugins.

It would be really nice indeed to have this working.

from bundle-tools.

i need also code splitting feature, i dont want to use i18n block, and i dont want to have huge files per language
splitting and merging in folder structure is absolutely needed feature

from bundle-tools.

This is a much needed feature for us. Is there a workaround for the meantime?

from bundle-tools.

any comment from creators? any ETA on this?

from bundle-tools.

I would love to see some progress on this matter as well. We are currently planning the transition to unplugin-vue-i18n and this is a major blockage on our roadmap. Any update on PR #274 ?

from bundle-tools.

In what order would the locale files be merged? This matters as duplicate keys would overwrite each other, at least in the implementation of #274.

from bundle-tools.