chore(deps): Bump prettier-plugin-apex

[keelerm84]

Note

Medium Risk
Primarily dev-tooling upgrades, but the updated dependency tree (notably joi) now requires Node >=20, which could break installs/CI environments on older Node versions.

Overview
Renames the npm package to launchdarkly-apex-server-sdk, marks it private, and bumps dev formatting tooling (prettier to 3.8.2, prettier-plugin-apex to 2.2.6).

Regenerates package-lock.json, pulling in new/updated transitive deps (including platform-specific optional @prettier-apex serializer binaries) and updating engine constraints (e.g., joi now requires Node >=20).

^{Reviewed by Cursor Bugbot for commit 1b6e568. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

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

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

^{Reviewed by Cursor Bugbot for commit 3eb94b9. Configure here.}

[cursor]

Lockfile incorrectly marks prettier as peer-only dependency

Medium Severity

The prettier entry in package-lock.json has a new "peer": true flag, but prettier is a direct devDependency in package.json. This flag indicates prettier exists only as a peer dependency of prettier-plugin-apex, which is incorrect. This lockfile inconsistency could cause prettier to be skipped during npm ci --omit=peer or pruned unexpectedly, breaking the prettier:format and prettier:check:ci scripts. The lockfile likely needs to be regenerated cleanly.

Additional Locations (1)

• package.json#L6-L7

 

^{Reviewed by Cursor Bugbot for commit 3eb94b9. Configure here.}

[keelerm84]

I cleared and regenerated this lock file and it was exactly the same. I think this is a false positive.