Zig env's output is no longer json

[tw4452852]

With ziglang/zig@0fb7a0a, zig env will not output json anymore, we need to find a better way to accomodate this change when we try to detect cache directory:

setup-zig/common.js

Lines 204 to 211 in 475c97b

	await exec.exec('zig', ['env'], {
	listeners: {
	stdout: (data) => {
	env_output += data.toString();
	},
	},
	});
	return JSON.parse(env_output)['global_cache_dir'];

[mlugg]

I'll try and get on this today; sorry in advance if there's a brief period of breakage once Zig builds are up. I'll just regex it out for now (zig env outputs nicely formatted ZON so it's not too tricky!), though I might later write an actual ZON parser in JS to be more confident in its resilience.

[tw4452852]

Maybe this is not the right place to purpose, instead of working out a zon parser in another language (JS in this case), can zig env offer a paramter to only output the specified field in plain text, something like this: zig env .global_cache_dir?

[Snektron]

Is there not yet a sort of standard "toolbox" for working with ZON? The standard library already contains a bunch of these things, so I'm thinking about something which can just expose those, so that you can run zig env | zig zon to-json or whatever.

[tw4452852]

AFAIK, not yet.
Currently I have to use a makeshift zon-to-json converter to handle build.zig.zon: https://gist.github.com/tw4452852/b24e96f6eb39193a658fd4e837158cc5

[squeek502]

There's an existing ZON parser written in TypeScript if that's helpful at all: https://github.com/nurulhudaapon/zzon

[mlugg]

Sorry for the instability here, folks! I've had a busy few days so didn't manage to get to this before the breakage hit everyone.

I'm just now finishing up a hacky implementation which should un-break the Action for the time being. #50 will track implementing an actual ZON parser, and I hope to get to that soon.

[mlugg]

Solved in v2.0.5 by 8d6198c. #50 tracks the better solution of an actual ZON parser.