Unexpected new line in function body with chained expression

Prettier 2.0.5
Playground link

--parser babel
--tab-width 4

Input:

// Small example.
transform((test) => test
    .method1("test", "in", "blah")
    .method1("another", "word")
    .method2()
    .method2());

// More realistic case.
const getQuery = builder("supernova")
    .select("name")
    .select("magnitude")
    .filter("and", (filter) => filter
        .condition("eventtype", "eq", 1)
        .filter("or", (filter) => filter
            .condition("date", "gt", "1998-01-01T00:00:00.000Z")
            .condition("magnitude", "lt", 2.72)
        )
    );

Output:

// Small example.
transform((test) =>
    test
        .method1("test", "in", "blah")
        .method1("another", "word")
        .method2()
        .method2()
);

// More realistic case.
const getQuery = builder("supernova")
    .select("name")
    .select("magnitude")
    .filter("and", (filter) =>
        filter
            .condition("eventtype", "eq", 1)
            .filter("or", (filter) =>
                filter
                    .condition("date", "gt", "1998-01-01T00:00:00.000Z")
                    .condition("magnitude", "lt", 2.72)
            )
    );

Expected behavior:

I'd prefer it look like the input. The line break in the arrow functions doubles the nesting of the inner expressions and can often lead to more unnecessary line breaks.

#5733 looks similar to my issue, but I don't know if the inner expressions are "fat" or not.

Possible conflicts

If this is changed outside of being used in a function argument, there may be other cases to consider and then I can certainly see arguments for not changing this behavior. For example, it can make it harder to differentiate function arguments from the body itself:

Input

const codeBlock = (loadLibraries) => (loadExternalData) => loadLibraries()
    .then(library => {
        ...
    })

Output

const codeBlock = (loadLibraries) => (loadExternalData) =>
    loadLibraries().then((library) => {
        ...
    });

Start with the linked Prettier Playground reproduction using the babel parser, comparing the input and output for chained expressions inside arrow-function arguments. Review the related #5733 issue for context, then confirm that the formatter preserves the requested nesting without regressing the possible conflict example.