miniflare should stringify all env vars

[ozburo]

Hello there!

Cloudflare stringyfies all environment variables, but miniflare respects/maintains the var type.

This might cause confusion/bugs and detours from what's expected when using wrangler etc.

[vars]
MY_VAR = true

Using miniflare:

console.log(typeof env.MY_VAR) // boolean

Using wrangler:

console.log(typeof env.MY_VAR) // string

It's not a huge thing but I thought I'd mention it.

Thanks again for this project, it's been a life saver!

[mrbbot]

Hey! 👋 Great catch! I'll definitely fix this in the next version. I guess just use "true" for now... 😅
Glad it's helped you out. 🙂

[mrbbot]

Hey! 👋 The first pre-release of Miniflare 2 has just been released, including this change. You can find the full changelog here and install it with npm i miniflare@next -D. Please let me know if you have any other issues, and feel free to ask questions in the #miniflare channel of the Cloudflare Workers Discord server.

[null-prophet]

Hey I have been working with honojs and cloudflare recently and I have noticed that env vars like booleans (mapped in a bindings.d.ts ) are mapped to true objects like boolean when I run on the command line but no in miniflare.

Is this some kind of regression or am I doing something wrong?

The issue on the honojs site outlines the full scenario.