Given that react-localization does not have date and number format and is heavily dependent on one developer we decided to switch to react-intl because it seems
ape
public
executionengineexception
class-visibility
targeting
verilator
splidejs
azure-virtual-machine
selenium4
knowledge-management
microsoft365
boost-python
angular-cli-ghpages
duplicates
blame
akka-stream
nyc
azure-public-ip
overhead
drupal-taxonomy
long-path
word-cloud
rabbitmq.client
continuation-passing
bond
doc
fastled
wpa
rendezvous-hash
rails-authorization