Update Render deploy guide to account for Astro 2.0 Node.js version requirement #2487
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for astro-docs-2 ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
|
Thanks for this - this is a necessary disclaimer, and thanks for using our existing format. (Interesting that both platforms hide this behind an advanced button!) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of changes does this PR include?
Description
This PR is a follow-up of withastro/astro#6004 and this Discord support thread.
It is currently not possible to deploy a project using Astro 2.0 to Render by blindly following the guide due to the fact that Astro 2.0 requires at least Node.js 16.12.0 and Render using by default Node.js version 14.
The proposed change is heavily inspired by the existing Cloudflare Pages deploy guide which has the same issue that is solved using an environment variable specifying the Node.js version added after clicking on an
Advancedbutton in the UI, which is the exact same process on Render. Other solutions are also suggested with links to the relevant Render documentation describing how to use them.