Update Money Dev Kit to 0.18.0

[sbddesign]

Summary

Bumps @moneydevkit/nextjs from ^0.16.0 to ^0.18.0 (latest).

Details

• No code changes required. The 0.17.0/0.18.0 changes to MDK are additive — new programmaticPayout() and getBalance() server helpers we don't use. The one internal type rename (PaymentConfig → WithPaymentConfig) doesn't affect us: our withDeferredSettlement call still type-checks, and the SettleResult type we import is unchanged.
• Peer deps (next, react, react-dom) are identical across 0.16–0.18; no other bumps needed.
• Env vars (MDK_ACCESS_TOKEN, MDK_MNEMONIC) unchanged.

Testing

• pnpm build ✅ — TypeScript compiles, all 27 routes generated, no errors.

Summary by CodeRabbit

• Chores
  • Updated @moneydevkit/nextjs to a newer compatible version.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
freeport	Ready	Preview, Comment	May 25, 2026 12:41am

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR updates the @moneydevkit/nextjs dependency version in package.json from ^0.16.0 to ^0.18.0. This is a minor version bump that allows the project to use newer features or fixes from the upstream package.

Changes

Dependency Version Update

Layer / File(s)	Summary
@moneydevkit/nextjs version bump package.json	Dependency version updated from ^0.16.0 to ^0.18.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Hops of joy for deps so new,
From sixteen up to eighteen true,
No breaking changes in sight,
MoneyDevKit shines so bright!
A tiny bump, a boundless flight! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating the Money Dev Kit dependency from 0.16.0 to 0.18.0, which is the primary and only modification in this pull request.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch worktree-update-mdk

⚔️ Resolve merge conflicts

• Resolve merge conflict in branch worktree-update-mdk

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Line 16: Update runtime verification after bumping "`@moneydevkit/nextjs`" to
^0.18.0 by performing a focused smoke test: install dependencies and run the
app, then exercise payment flows end-to-end — create a checkout and confirm
redirect behavior, verify client hooks/useCheckoutSuccess return expected
success state in post-checkout pages, and validate server/client behavior of
withDeferredSettlement (deferred settlement callbacks and webhooks) against your
payment sandbox; if any behavioral/API differences appear, pin or adapt code
paths referencing useCheckoutSuccess, withDeferredSettlement, and checkout
creation/redirect handling to match the new package's contract.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 4118fd3d-d951-4dc7-9dfc-b2004cd0b439

📥 Commits

Reviewing files that changed from the base of the PR and between 98379c0 and 66027bc.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• package.json

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash# Check npm registry for `@moneydevkit/nextjs` version 0.18.0 and any security infoecho"=== Checking version 0.18.0 exists ==="
npm view `@moneydevkit/nextjs`@0.18.0 version
echo -e "\n=== Checking for security advisories ==="
npm audit --json --package-lock-only 2>/dev/null | jq '.vulnerabilities // "No vulnerabilities found in audit"'echo -e "\n=== Checking latest version ==="
npm view `@moneydevkit/nextjs` version
echo -e "\n=== Checking peer dependencies for 0.18.0 ==="
npm view `@moneydevkit/nextjs`@0.18.0 peerDependencies

Repository: ATLBitLab/freeport

Length of output: 827

---

@moneydevkit/nextjs 0.18.0 bump: security check looks clean; still smoke-test payment runtime

• @moneydevkit/nextjs@0.18.0 exists on npm and its peer deps align with Next/React (next '^15 || ^16', react '^18 || ^19', react-dom '^18 || ^19').
• npm audit reports no known vulnerabilities.
• Build success covers compile-time compatibility, but validate runtime payment flows (checkout create+redirect, useCheckoutSuccess, and withDeferredSettlement) to catch any behavioral/API contract changes.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@package.json` at line 16, Update runtime verification after bumping
"`@moneydevkit/nextjs`" to ^0.18.0 by performing a focused smoke test: install
dependencies and run the app, then exercise payment flows end-to-end — create a
checkout and confirm redirect behavior, verify client hooks/useCheckoutSuccess
return expected success state in post-checkout pages, and validate server/client
behavior of withDeferredSettlement (deferred settlement callbacks and webhooks)
against your payment sandbox; if any behavioral/API differences appear, pin or
adapt code paths referencing useCheckoutSuccess, withDeferredSettlement, and
checkout creation/redirect handling to match the new package's contract.