Incompatibility with `yajl` introduced in `json 2.11.0`

[weshatheleopard]

> require 'json'; JSON::VERSION
=> "2.6.3"
> JSON["1"] # Works fine
=> 1
> require 'yajl/json_gem'
=> true
> JSON["1"] # Works fine
=> 1
> require 'yajl/version'; Yajl::VERSION
=> "1.4.3"

Whereas

> require 'json'; JSON::VERSION
=> "2.19.5"
> JSON["1"] # Works fine
=> 1
> require 'yajl/json_gem'
=> true
> JSON["1"] # Errs out
TypeError: wrong argument type nil (expected Hash)
from /[...]/.bundle/gems/ruby/3.3.0/gems/yajl-ruby-1.4.3/lib/yajl.rb:44:in `new'
> require 'yajl/version'; Yajl::VERSION
=> "1.4.3"

The problem was introduced in 2.11.0 by this change.

Yes, I do understand this is a highly unlikely circumstance... but we have quite obviously ran into it!

[byroot]

So I could of course revert part of that change to solve this, but ultimately this is a bug in YAJL as it is the one that moneky patch into json so it's on them to be compatible.

That being said, can I ask why would you even consider patching JSON to use YAJL under the hood? It's much slower and barely maintained anymore. I understand using YAJL for some of its streaming APIs etc, but not for replacing JSON.parse.