OpenReceive 0.4.21 fixes openreceive doctor right after a Next.js integration. Doctor now reads the codes from .env.local (or .env) itself, so an agent no longer loads the file into a shell, where the & in each code split the values and printed pieces of them. The agent directions also end on a short closing message that keeps the test order and does not call stablecoins unavailable over one coin's swap minimum. Upgrade if you run doctor from a project that keeps its codes in an env file.
Optional swaps let payers use USDT, USDC, SOL and ETH; a configured swap provider converts them to BTC over Lightning in the merchant's connected wallet. Asset and network availability depends on the provider.
- Fixed:
openreceive doctorread only the process environment, so right after a Next.js integration, with both codes in.env.local, it reportedNWC_URImissing. One agent then sourced the file into bash. The&in each URI split the values and printed pieces of both codes on screen. Doctor (anddebug-report) now fillsNWC_URI,LSC_URI_PRIMARY,LSC_URI_BACKUPandOPENRECEIVE_ALLOW_SPEND_CAPABLE_NWCfrom.env.local, then.env, in the working directory. The order is Next's, and a variable the environment already sets wins. A newenv files:line names the files it used and never prints a value. The Node, Fastify and Next.js directions say doctor reads the file itself and never to source it. - Changed: the closing "Setup is finished" message in every library stack's directions is at most five lines and does not list what changed. It keeps the test order, because the link is that order. It names the methods the checkout offers. Agents had been writing 30-line wrap-ups, deleting the order behind the link, and calling stablecoins unavailable on a $1–$7 shop because of one coin's swap minimum. The checkout already shows a minimum on that coin's own tile.
- The Next.js directions eval shop now runs Next.js 16, which builds with Turbopack, as new apps do. Turbopack is the bundler that broke wallet preflight before 0.4.19.
