v6.5.1

Patch Release

• fix(deps): update prisma monorepo to v5.7.0 #9642

  Users were facing issues deploying to Netlify on Node.js 20. Prisma would fail during runtime saying it couldn't locate the engine binary. This Prisma minor includes the fix; read more in the Prisma release notes.

  (Note that Redwood doesn't officially support Node.js 20 yet, but their deploys were upgrading from underneath them due to the unpinned .nvmrc; see v6.4.2)

• fix(cli): avoid calling rw-vite-build via yarn #9624 by @jtoar

  This PR starts optimizing Redwood's memory usage during build. Redwood has always had memory problems on certain deploy providers. But many users have reported that v6 seems to be more problematic than usual. To address this, we started profiling CLI commands, looking at the amount of memory used and the number of processes spawned, starting with yarn rw build. We found that using yarn internally to call a binary seemed to increas memory by ~100 MB compared to using node. The number of processes spawned also dropped by two with this change. While this is far from conclusive, we'd like to get this change in an RC to see if it makes a noticeable difference for users.

  (If you're interested in profiling the amount of memory used by CLI commands, now's a great time to contribute!)

• fix(CLI): merge NODE_OPTIONS in yarn rw dev #9585 by @jtoar

  This PR merges user-specified NODE_OPTIONS with Redwood's, which is just the --enable-source-maps option:

  NODE_OPTIONS="--no-experimental-fetch" yarn rw dev
  # Resulting NODE_OPTIONS: --no-experimental-fetch --enable-source-maps
  

• chore: Update Testing documentation to link to How to Test Email/Mailer #9634 by @dthyresson