Using multiple languages with new projects feature

[paulGeoghegan]

Hi, I was wondering how using projects works with multiple languages. Previously you would include the /translations/es script for example but for projects theres no place to select what languages to include.

[claviska]

We've debated solving this in a couple different ways and would love your thoughts on this idea. This is, of course, in the context of Web Awesome projects (our hosted service).

We could provide a copy/paste import map folks can put on the page that let's them do something like this:

import { thing1, thing2 } from '@awesome.me/webawesome';

Then translations could be imported as usual but, thanks to the import map, it would route to your kit.

import '@awesome.me/webawesome/dist/translations/de.js';

I don't think we want to generate and inject the import maps since they need to be assigned before any imports occur.

Any thoughts or alternate ideas?

[paulGeoghegan]

I'm not against this but I would have liked to be able to select languages from a list of checkboxes on the project website so I can modify it during runtime and not mess around with importing languages given that kin of removes the point of the one line project.
Obviously not really I just feel like if you can avoid it you should.
In reality imports are fine so whatever works for you guys.

[claviska]

Great point. We can definitely add translations to the projects UI. I got hung up on how folks can import things like allDefined and similar utilities that need to be imported at runtime.

Adding this to the list 😄

[paulGeoghegan]

Perfect, excited to hear more about this. Sorry I never replied.