Internal config-loading state now tracks a lastGetConfigOutcome enum with values "parsed", "parse-error", "read-error", and "enoent", replacing the previous boolean lastGetConfigWasParseError. Callers now branch on both parse-error and read-error cases to trigger fallback-to-cache behavior, where previously only parse errors did, and the outcome is surfaced as a readRejected flag alongside the returned config.
Config load now distinguishes parse errors from read errors
Config loading now distinguishes read errors from parse errors, and both trigger the fallback-to-cache path.
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ConfigurationArea: what it touches
Internal ChangesKind: in v2.1.259,
Internal ChangesSection of the release