Running CLI on main branch crashes with Invalid response content-type (got null)

[ThisIsMissEm]

This bug was introduced with the ATCute upgrade in #14

node dist/bin.js setup
✔ DID or handle of the account to use: … @test.thisismissem.social
✔ Account password (cannot be an app password): … *******************
file:///labeler/node_modules/.pnpm/@atcute+client@4.0.5/node_modules/@atcute/client/dist/client.js:79
                            throw new TypeError(`Invalid response content-type (got ${type})`);
                                  ^

TypeError: Invalid response content-type (got null)
    at #perform (file:///labeler/node_modules/.pnpm/@atcute+client@4.0.5/node_modules/@atcute/client/dist/client.js:79:35)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async plcRequestToken (file:///labeler/dist/scripts/plc.js:117:5)
    at async file:///labeler/dist/bin.js:41:5

Node.js v22.14.0

The com.atproto.identity.requestPlcOperationSignature does not actually return a JSON response, and if I use:

export async function plcRequestToken(credentials: LoginCredentials): Promise<void> {
	const { agent } = await loginAgent(credentials);
	await agent.post("com.atproto.identity.requestPlcOperationSignature", { as: null });
}

The crash still occurs as the as: null seems to get overwritten to as: 'json', which I think is an underlying bug in atcute.

Then the problem is resolved (patch incoming)

cc @mary-ext

[ThisIsMissEm]

@mary-ext actually, ignore that. I forgot to recompile the code after swapping to as: null 🤦🏻‍♀️