The method is quite new, so the rule cannot be in the recommended preset, and we should add a note in the docs about it being quite new.

This pattern seems rarely used.

https://github.com/search?q=new Response(JSON.stringify&type=code&p=1

For what purpose are you Response like that? I don't see the use case. Usually, Response.json(), without arguments is used to parse a response, but why would one ever need to construct it?

There are two json() methods in the Response class:

• static Response.json(data, init): Create a response that contains JSON.
• Response.prototype.json(): Parse the JSON in the body of the response.

In my unit tests, I mock the fetch method to return a specific JSON (examples in Cast Kodi):

it("should return video URL", async function () {
    const stub = sinon.stub(globalThis, "fetch").resolves(new Response(
        JSON.stringify({
            media: [{
                id:          "foo",
                offline_url: "http://bar.com/baz.mp4",
            }],
        }),
    ));

    const file = await scraper.extract("https://watch.pokemon.com/player?id=foo");
    assert.equal(file, "http://bar.com/baz.mp4");

    assert.equal(stub.callCount, 1);
    assert.deepEqual(stub.firstCall.args, [
        "https://www.pokemon.com/api/pokemontv/v2/channels/uk",
    ]);
});

With this new rule, the above code would be in error. The code can be simplified to:

it("should return video URL", async function () {
    const stub = sinon.stub(globalThis, "fetch").resolves(Response.json({
        media: [{
            id:          "foo",
            offline_url: "http://bar.com/baz.mp4",
        }],
    }));

    // ...
});

I see. Yes I suspected the primary use case for this is mocking. So I'm neutral on this one, don't see it much in demand, thought.

Deno says: "This addition to the Fetch specification was specifically designed with server side runtimes in mind." Deno 1.22 Release Notes - New Response.json() static method.

For example:

import { serve } from "https://deno.land/[email protected]/http/server.ts";

const port = 8080;

const handler = (request) => {
    const body = { userAgent: request.headers.get("user-agent") ?? "Unknown" };

    // Previously:
    // return new Response(JSON.stringify(body), {
    //     headers: { "content-type": "application/json" },
    // });

    // Now:
    return Response.json(body);
};

await serve(handler, { port });

Yeah, for servers that support Response for actually responding, it's definitely useful.