In light of #11304, it's probably worth checking if we can easily similarly address all other places where the package behaves this way for the sake of consistency. It's OK if the outcome is that we leave some of them as-is, but internal sentiment is we should be moving to always toJSON(false)