Gabriel Haruki

Since this repo looks unmaintained I made a [fork](https://github.com/Harukisatoh/i18next-scanner-fix) of it that solves this issue, and I'm also publishing this fix into npm as [i18next-scanner-fix](https://www.npmjs.com/package/i18next-scanner-fix). Currently, the solution implemented into...

For me, the issue was happening with a local file, which doesn't make sense as in my opinion, this security feature should only apply to cross-origin content. But I managed...

Same here. And if you focus on Select and then click on another focusable component, both will stay focused

> @wsldr1 The extension code posted in the gist link above works in 2 scenarios: > > 1. The extension works as expected in Chrome, and is what the expected...

I've been experimenting with this feature recently, and it's fantastic! However, I believe I've come across a potential issue. To be honest, I'm not entirely sure if it's an actual...

Hey guys, I was having the same issue as described in this thread. But I managed to solve the problem. So, for future readers, this issue seems related to #607....

Hey guys, thank you for the examples, they pointed me to the right direction. I still have one issue though, I was able to inject the 'wppconnect-wa.js' module on the...

> any update on this question? Unfortunately no, as for my case middlewares weren't really needed, I just stopped using them. But if you find a way to solve this...

When is the next version coming out? Btw, thanks @AnMiZa for the fix.

> That happens all the time when the type version of different modules mismatch for any reason, whether the changes are breaking or not. > > It will get fixed...