Christoph Tavan

Still an issue for me as well. Anything we could contribute to get this fixed?

For anyone bumping into this, https://github.com/bundlewatch/bundlewatch might be an alternative.

I believe the whole idea of this module is to provide a RNG that is guaranteed to be a [CSPRNG](https://en.wikipedia.org/wiki/Cryptographically_secure_pseudorandom_number_generator). Providing a JS fallback would precisely remove the guarantee that...

@messerm @daliusd and for those interested I've proposed a patch for the latest `acorn-jsx` in #112 If you can't wait, try `npm install @contentpass/i18next-scanner`. Would be curious to hear if...

Since my patch has been released, can you check again with `[email protected]`? Should solve most issues with modern JavaScript. Typescript will likely require some more love.

@NickNaso are there any plans to resolve this issue or is there anything I could contribute? This one is currently blocking https://github.com/grpc/grpc-node/issues/778 which in turn is causing other trouble further...

@nayaabkhan I see you have started a Typescript-Rewrite. I do have some interest in getting rid of the `componentWillReceiveProps` deprecation warning so I was wondering if you are palling to...

@nayaabkhan I just realized that in https://github.com/nayaabkhan/react-polyglot/commit/9210c448b07c5810b97a162e297dc100c3959036 componentWillReceiveProps was replaced by componentDidUpdate. This means that with 0.6.0 the react deprecation warning is gone. I'm still a bit concerned whether `componentDidUpdate`...

Thanks! Which means we still need a different way of doing this in order to remain compatible with `react>=17`…

@soda0289 I took this over to #38 to not further hijack this TypeScript pull request, let's continue the discussion over there.