Nico Wiedemann

npm support would be great, indeed!

I can only [quote](https://github.com/strapi/strapi/issues/10322#issuecomment-885692429) @terion-name > @sam-pires are there any plans to rework entire i18n model? absence of parent id of an entity with localizations is a huge pain, including...

> Is not being able to reference a relationship entity from a different locale an intented bahaviour? If it's a an issue, is it related to [Field localization](https://github.com/strapi/strapi/issues/12538) ? It...

While i18n is a plugin it is heavily integrated into strapi. It adds a lot of complexity to do this right and they decided not to address this. Unfortunately this...

> Hopefully they are going to address this. A current workdaround is to add localized field to the collection type. e.g. name_en, name_de to avoid using 18n at all. I...

I have the same problem using LESS.

I think it should be noted that the limits for SQLite are almost doubled. This means that - as many use SQLite during development - this first pops up when...

I disagree. This behaviour currently breaks the whole setup on deployment and requires fundamental code changes late in the development process. There should *at least* be warnings that output in...

You didn't say you plan to warn users. Good to hear that you agree. I also encourage you to note these limits in the documentation as it will be breaking...

I am currently using Version 2, but I think it would be a good addition for both.