direnv-mode tries to parse direnv errors

I've been experiencing a direnv configuration error, beyond the scope of this report. (FYI, "direnv export json" is erroring out for me with: Couldn't find a configuration directory for direnv)

When this happens, the problem is compounded by direnv--export trying to parse the stderr output. The symptom is that re-search-backward can't find "^{".

Does it make sense to refrain from parsing when exit-code is nonzero?