-
Notifications
You must be signed in to change notification settings - Fork 13.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deployment: Add a note about PaaS default nodejs version #28720
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
@@ -237,6 +237,12 @@ In most cases, you'll be running into errors that thousands of developers have e | |||||||||
|
||||||||||
There are two stages of the deployment process where you are most likely to encounter problems. These are during deployment and right after. | ||||||||||
|
||||||||||
<div class="lesson-note" markdown="1"> | ||||||||||
|
||||||||||
Depending on the host provider you use, the default NodeJs engine version might not be the LTS version. Additionally, depending on the NodeJs features you’re using, you might need to specify the NodeJs version to utilize those features. | ||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. General suggestions for wording of the point, plus a nice link to how to actually specify compatible versions. Plus, instead of "NodeJs" or "NodeJS", it should either be "Node.js" or just "Node" for consistency across documentation I think. I don't mind either and have used "Node" in the suggestion below. Whatever we end up using, would you mind also amending any other mentions of "NodeJS" in the lesson if there are any?
Suggested change
|
||||||||||
|
||||||||||
</div> | ||||||||||
|
||||||||||
#### On deployment | ||||||||||
|
||||||||||
If you run into an error while deploying, the first thing to do is to check the build logs. Finding the build logs should be easy; it's the stream of output you'll see after kicking off a new deployment. | ||||||||||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note to self: Look into making warning note boxes more visually distinct from standard note boxes.