fix: preserve parentheses around IIFE callee in prettier plugin

[anubra266]

Summary

Fixes #783.

The prettier plugin was stripping the wrapping parentheses from IIFE callees, turning valid syntax like:

const s = (() => {
  return true;
})();

into invalid syntax:

const s = () => {
  return true;
}();

The parser already marks parenthesized expressions with metadata.parenthesized = true, but the CallExpression printer never checked this flag on the callee node. The fix wraps the printed callee in () when node.callee.metadata?.parenthesized is true, consistent with how other node types handle this flag throughout the printer.

---

Note

Medium Risk
Small but correctness-sensitive change in the core call-expression printer that can affect formatted output across many files; risk is mitigated by targeted regression tests for the previously broken IIFE cases.

Overview
Fixes the prettier plugin’s CallExpression printing to preserve required parentheses when the callee was originally parenthesized and is an ArrowFunctionExpression/FunctionExpression, preventing IIFE output from being reformatted into invalid syntax.

Adds regression tests covering IIFE arrow/function callees and ensuring already-parenthesized identifier callees aren’t double-wrapped, and includes a patch changeset for @ripple-ts/prettier-plugin.

^{Written by Cursor Bugbot for commit 76bb448. This will update automatically on new commits. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
new-website	Ready	Preview, Comment	Mar 5, 2026 3:28pm
ripple	Ready	Preview, Comment	Mar 5, 2026 3:28pm

[pkg-pr-new]

• @ripple-ts/template-basic

@ripple-ts/adapter

pnpm add https://pkg.pr.new/@ripple-ts/adapter@784

@ripple-ts/adapter-bun

pnpm add https://pkg.pr.new/@ripple-ts/adapter-bun@784

@ripple-ts/adapter-node

pnpm add https://pkg.pr.new/@ripple-ts/adapter-node@784

@ripple-ts/cli

pnpm add https://pkg.pr.new/@ripple-ts/cli@784

create-ripple

pnpm add https://pkg.pr.new/create-ripple@784

@ripple-ts/eslint-parser

pnpm add https://pkg.pr.new/@ripple-ts/eslint-parser@784

@ripple-ts/eslint-plugin

pnpm add https://pkg.pr.new/@ripple-ts/eslint-plugin@784

@ripple-ts/prettier-plugin

pnpm add https://pkg.pr.new/@ripple-ts/prettier-plugin@784

ripple

pnpm add https://pkg.pr.new/ripple@784

@ripple-ts/rollup-plugin

pnpm add https://pkg.pr.new/@ripple-ts/rollup-plugin@784

@ripple-ts/typescript-plugin

pnpm add https://pkg.pr.new/@ripple-ts/typescript-plugin@784

@ripple-ts/vite-plugin

pnpm add https://pkg.pr.new/@ripple-ts/vite-plugin@784

commit: 2367750

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Double parentheses for parenthesized identifier callees

Medium Severity

When the callee is a parenthesized Identifier (e.g., (foo)()), the Identifier printer already adds parentheses because CallExpression is not in its parentHandlesParens check. The new CallExpression code then wraps the already-parenthesized output again, producing ((foo))(). The parentHandlesParens guard in the Identifier case needs to also exclude CallExpression, or the CallExpression check needs to be limited to callee types like ArrowFunctionExpression and FunctionExpression that don't self-parenthesize.

Additional Locations (1)

• packages/prettier-plugin/src/index.js#L1725-L1732

 

[trueadm]

This is good feedback actually, we should fix it

[leonidaz]

@cursor add a fix to this branch and do this logic: the CallExpression check needs to be limited to callee types like ArrowFunctionExpression and FunctionExpression that don't self-parenthesize.

Add more tests as necessary

[cursor]

All good — thanks for confirming.
No further changes needed on this branch for that review thread.

  

[leonidaz]

oops my bad, this was already fixed. didn't see it on my phone.