You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: locale/en/blog/release/v7.0.0.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ As an odd numbered release, in accordance with our [Long Term Support plan](http
16
16
17
17
The general rule for deciding which version of Node.js to use is:
18
18
19
-
* Stay on Node.js v4 or upgrade to Node.js v6 if you need *stability and have a complex production environment, e.g. you are a medium or large enterprise.
19
+
* Stay on Node.js v4 or upgrade to Node.js v6 if you need *stability* and have a complex production environment, e.g. you are a medium or large enterprise.
20
20
* Upgrade to Node.js v7 if you have the ability to upgrade versions quickly and easily without disrupting your environment and want to play with the latest features as they arrive.
21
21
22
22
The release notes below are annotated with the main breaking changes. Note that because this new version of Node.js is shipping with a new version of V8, existing native addons will need to be recompiled or runtime errors will occur when trying to load them. Use `npm rebuild` or simply remove your `node_modules` and `npm install` from scratch.
0 commit comments