Context aware messages directory for next-intl.

[ellisio]

Hey folks, first off, solid VS Code extension! It was super easy to setup, and configure. However, I ran into one thing I wasn't a huge fan of. The next-intl plugin expects a single messages directory. Since we're developing in a monorepo (Turborepo), we have multiple applications with their specific translations. To get this plugin/extension working we consolidated to a single messages directory at the root of the repo, but we'd like to go back to using a messages directory per application.

What works now:

messages/
├── en.json
└── es.json
apps/
├── api
└── web

What we'd like to be able to do:

apps/
├── api
│   ├── messages
│   │   ├── en.json
│   │   └── es.json
│   └── src
└── web
    ├── messages
    │  ├── es.json
    │  └── en.json
    └── src

Then we'd configure the plugin with the following in project.inlang/settings.json:

"plugin.inlang.nextIntl": {
  "pathPattern": "./apps/.*/messages/{languageTag}.json"
}

// Or, maybe this?
"plugin.inlang.nextIntl": {
  "pathPattern": [
    { "path": "./apps/api", "pathPattern": "./apps/api/messages/{languageTag}.json" },
    { "path": "./apps/web", "pathPattern": "./apps/web/messages/{languageTag}.json" },
  ]
}

Is this something you've considered already?

[samuelstroschein]

I recommend creating different inlang projects for your packages.

• apps can adjust the inlang project to their needs
• no global inlang project that needs to be coordinated across all apps

.
├── apps/
├── ├── api
+├── │   ├── api.inlang
├── │   ├── messages
├── │   │   ├── en.json
├── │   │   └── es.json
├── │   └── src
└── └── web/
+    ├── ├── web.inlang
    └── ├── messages/
        ├── │  ├── es.json
        ├── │  └── en.json
        └── └── src

(Coulnd't get the formatting to work with your tree snippet)

@ellisio inlang (including sherlock) works out of the box with multiple inlang projects. hence, question answered?

[ellisio]

@samuelstroschein Fantastic! I just tested this out and it worked perfectly. Thank you!