As a setup I was working on apparently relied on parsed being undefined in this case, installing this patch version broke it.
Could it be worth reverting this part of the fix? Or is the risk of someone running into this rather small as parsed being undefined was not documented behavior?
16.4.5 changed the error case of
config()from returning{ error: Err }to{ error: Err, parsed: {} }.As a setup I was working on apparently relied on
parsedbeingundefinedin this case, installing this patch version broke it.Could it be worth reverting this part of the fix? Or is the risk of someone running into this rather small as
parsedbeing undefined was not documented behavior?