{"version":"2.1.228","anchor":"env-vars-set-to-an-empty-string-now-count-as-unset","canonical_anchor":"env-vars-set-to-an-empty-string-now-count-as-unset","heading":"Env vars set to an empty string now count as unset","tier":"notice","area":"Configuration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/env-vars-set-to-an-empty-string-now-count-as-unset","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Env vars set to an empty string now count as unset\n\nEnvironment variables set to an empty string now count as unset and use the default.\n\n**What**\n\nTwo environment-reading helpers changed so that a variable set to an empty string or to whitespace reads as absent and the default applies, rather than yielding an empty value.\n\n**Details**\n\n- The Deno code path also gained the same fallback, which it was missing.\n\n**Evidence**\n\n`globalThis.Deno.env?.get?.(e)?.trim()`\n\n- Area: Configuration\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}