Add deno support to findConfigurationFlag

[bdchauvette]

Hi @lorenzofox3!

Thanks for such a great project. I've been using zora with ESBuild and it's such a breath of fresh air using tools that are so clean and so fast!

What this PR does

Adds support for loading configuration flags from environment variables when running zora in Deno.

Why

I've been using zora on a few projects and I really love it as a way to run tests that work in any JS environment.

For one of my projects (still private, unfortunately), I'm supporting Deno. zora itself has been working great with Deno -- at least when using a bundler; I haven't tried running it from e.g. unpkg -- but I'd like to be able to set configuration flags using environment variables.

Note that the change in this PR is just a minor DX improvement for packages that only target Node and Deno. It's not strictly necessary because Deno's supports using window as a global object, so doing something like this does work:

if (typeof window !== "undefined") {
  // @ts-expect-error
  window.INDENT = true;
}

It's relatively minor bit of boilerplate, and it's required when targeting browsers anyway, but I still wish I didn't need it for packages that don't intend to be run in browsers.

AFAIK, outside findConfigurationFlags, the rest of zora is Just JavaScript (:sparkles:), so I don't think Deno requires any additional changes to work with zora. However, I totally understand that you might not want to add the burden of having to support an additional runtime. Maybe this this could be a first step towards something like "experimental support for Deno"? 🤷

Anyway, thanks again for such a great project! Let me know if you have any questions.

Related

• Deno.env API

[bdchauvette]

In lieu of publishing my branch on npm so it can be consumed by Deno, here's a demo on repl.it with the bundle pasted in:

https://repl.it/@bdchauvette/zora-deno-config

[lorenzofox3]

Thanks a lot !

I thought Deno came with its own testing utilities. Why don't you use it

[bdchauvette]

Thanks!

Deno does come with a test runner, but I'm trying to make sure my tests can run in all of the targeted environments (node, deno, sometimes browser). If I used deno's built-ins, I wouldn't be able to run the suite in the other environments -- at least not very easily.