issue with a nested unary (not) condition

Prettier 2.0.5
Playground link

--parser babel

Input:

if (veryFirstCondition ||
   (guardCondition1 &&
   guardCondition2 &&
   guardCondition3 &&
   !(negativeTestCondition1 &&
    looooooooooongNegativeTestCondition &&
    negativeCondition3)) // <===
) {
  doSOmething()
}

Output:

if (
  veryFirstCondition ||
  (guardCondition1 &&
    guardCondition2 &&
    guardCondition3 &&
    !(
      negativeTestCondition1 &&
      looooooooooongNegativeTestCondition &&
      negativeCondition3
    )) // <===
) {
  doSOmething();
}

Expected behavior:

if (
  veryFirstCondition ||
  (guardCondition1 &&
    guardCondition2 &&
    guardCondition3 &&
    !(
      negativeTestCondition1 &&
      looooooooooongNegativeTestCondition &&
      negativeCondition3
    )
  ) // <===
) {
  doSOmething();
}

Something similar but without the veryFirstCondition part seems to be formatted correctly:

Prettier 2.0.5
Playground link

--parser babel

Input:

if (
   guardCondition1 &&
   guardCondition2 &&
   guardCondition3 &&
   !(negativeTestCondition1 &&
    looooooooooongNegativeTestCondition &&
    negativeCondition3)) {
  doSOmething()
}

Output:

if (
  guardCondition1 &&
  guardCondition2 &&
  guardCondition3 &&
  !(
    negativeTestCondition1 &&
    looooooooooongNegativeTestCondition &&
    negativeCondition3
  )
) {
  doSOmething();
}

I did try the same thing with the recent updates from the master branch, with the same result.

I think this is not a super major issue but it would be nice to see it fixed someday.

Reproduce the formatting difference from the linked Playground with the babel parser and the nested unary-condition input. Compare the actual output with the expected closing-parenthesis and comment placement, then locate the formatter tests covering similar conditional expressions and add a regression case whose output matches the expected example.