Bumping default version of OpenNext to 3.9.8

[leanderiversen]

The current default version (3.6.6) was released in June, so I think it's time to bump this to the latest version.

[vimtor]

thanks for your contribution @leanderiversen

i tried deploying multiple AWS Next.js examples and they seem to be working

any specific reason why you wanted the new OpenNext version? i'll try to get this merged but given how popular the Next.js construct is i'll need more testing

[leanderiversen]

Thanks for the testing, @vimtor. For my projects, I always manually specify the latest version of OpenNext, but considering someone new to SST, and potentially Next itself, it would be beneficial for them to use the latest version of OpenNext, considering the amount of patching that has been done for recent versions.

[vimtor]

closes #6348

[onhate]

Hey! Just a heads up - OpenNext 3.9.8 has a build issue that breaks projects using packages with native modules (like @swc/core from next-intl).

The error looks like this:

✘ [ERROR] No loader is configured for ".node" files: @swc/core-darwin-arm64/swc.darwin-arm64.node
✘ [ERROR] Could not resolve "@swc/wasm"

The root cause was that the compiled Next.js config patch wasn't properly inlining require.resolve calls, which caused esbuild to fail when trying to bundle dependencies with native bindings.

This was fixed in 3.9.9: opennextjs/opennextjs-aws#1077

Would be great to bump the default OpenNext version to 3.9.9+ to avoid this regression affecting other users.

[onhate]

As a temporary workaround, you can pin to the latest 3.x in your SST config:

new sst.aws.Nextjs('Web', {
  buildCommand: 'pnpm dlx @opennextjs/aws@3 build',
  // ...
});

This will use 3.9.14 (or latest) instead of the broken 3.9.8.