goamn

+1 for this, I am just starting out with i18next/locize and more options means more research between the scanner and the parser, kind of a waste of time. Please merge...

I have finished researching `i18next.parser` and `i18next-scanner`. I don't see the benefit of either package? They don't seem to handle dynamic keys (i.e. `t(enumString[enumIndex])`. It seems as though the inbuilt...

> We recommend using the locize-backend during development - and if preferred the http-backend for production (if hosting translations yourself)... > > saveMissing using http-backend to locize should be possible...

> > .... > > Please write an email at [[email protected]](mailto:[email protected]) and send your code snippets and possibly also the i18next debug output.... You may also compare it with this:...

I take my comments back regarding the i18next-parser. It is very useful on the initial localization of an application as you don't need to try to trigger ever warning, error,...

@devrnt Thanks Jonas this is great! Please don't delete the post as it was the only way I found out about it. I think it would be great if you...

I tried to upgrade to get the bugfix for this issue: https://github.com/html-to-text/node-html-to-text/issues/232 However I got the error mentioned in this issue. A simple hack for anyone else in my place:...

@KillyMXI I believe it was the latest version 8.2.1. I did not try v9 preview

> > If bun documented and supported a canonical way to run an npm audit over a bun.lockb in the near future, this would be a significant stopgap. As mentioned...

Can you please prioritise this? It's also happening for us. We just migrated to FluentUI v9. It happens when we set positioning "autoSize" to "height"