Skip to content

docs: add note about SSR when deploying to Amplify#3719

Merged
farnabaz merged 1 commit intonuxt:mainfrom
nimonian:docs/amplify-nodejs22-runtime
Feb 17, 2026
Merged

docs: add note about SSR when deploying to Amplify#3719
farnabaz merged 1 commit intonuxt:mainfrom
nimonian:docs/amplify-nodejs22-runtime

Conversation

@nimonian
Copy link
Copy Markdown
Contributor

🔗 Linked issue

#3718

❓ Type of change

  • 📖 Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • 👌 Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Resolves #3718

Ensures that users using SSR are advised to set the correct runtime version for Node in AWS Amplify deployments.

📝 Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@vercel
Copy link
Copy Markdown

vercel bot commented Feb 15, 2026

@nimonian is attempting to deploy a commit to the Nuxt Team on Vercel.

A member of the Team first needs to authorize it.

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new bot commented Feb 15, 2026

npm i https://pkg.pr.new/@nuxt/content@3719

commit: f64cec0

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Feb 15, 2026

📝 Walkthrough

Walkthrough

This pull request adds a warning block to the AWS Amplify deployment documentation that clarifies a Node.js version requirement when using Server-Side Rendering (SSR) with node:sqlite. The warning informs developers that Amplify's default Node 20 runtime is insufficient and must be explicitly configured to Node 22.x via the nitro.awsAmplify.runtime setting in nuxt.config.ts. The block is positioned before the "Option B: Use sqlite3" section to guide users before they encounter runtime incompatibility issues.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 6
✅ Passed checks (6 passed)
Check name Status Explanation
Title check ✅ Passed The title directly and clearly summarizes the main change: adding documentation guidance about SSR configuration for AWS Amplify deployments.
Description check ✅ Passed The description is directly related to the changeset, explaining that it resolves the linked issue by advising users to set the correct Node runtime version for SSR.
Linked Issues check ✅ Passed The PR successfully addresses all coding-related objectives from issue #3718: it documents the Node version requirement for SSR, explains the runtime configuration issue, and provides the required nuxt.config.ts configuration.
Out of Scope Changes check ✅ Passed All changes are in scope: the PR adds documentation content directly addressing the objectives in issue #3718, with no extraneous modifications.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into main

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

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


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

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

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (2)
docs/content/docs/6.deploy/8.aws-amplify.md (2)

38-48: Consider clarifying the build vs. runtime environment distinction.

The warning explains the runtime configuration requirement, which is distinct from the build environment configuration shown in lines 22-36. To help readers understand this important distinction more clearly, consider adding a brief note that emphasizes this is about the runtime environment (where SSR executes), not the build environment (where the app is compiled).

For example:

::warning
If you are using SSR for content, Nitro defaults the Amplify **runtime environment** (where SSR executes) to Node 20, even if your build environment uses Node 22. Since `node:sqlite` requires Node 22+, you need to explicitly set the runtime version in `nuxt.config.ts`:

39-39: Consider clarifying "using SSR for content."

The phrase "using SSR for content" might be interpreted differently by readers. Consider being more explicit, such as "when using Server-Side Rendering with Nuxt Content" or "when SSR is enabled and querying content at runtime."

@farnabaz farnabaz merged commit 5b75ffd into nuxt:main Feb 17, 2026
5 of 6 checks passed
@nimonian nimonian deleted the docs/amplify-nodejs22-runtime branch February 17, 2026 23:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

AWS Amplify deployment: node version mismatch in build vs runtime

2 participants