kdasg.blogg.se

V14 has an extra year of lifespan over v12, but was only released last month, so i prefer12 for stability. I could install v13 or v14 (both are current) but v13 is already in maintenance and will reach EOL next month. I am installing node v12 which is Active LTS and has been established for a year at time of writing, and 2 years from End of Life. Next we'll Use “n” to install node (at least version 8 for react)Ĭheck for latest stable releases of Nodejs here: Updating Nodejs via "n" Node Version Manager

Create-react-app wont run on node less than v8, so there as no choice.īelow I'll explain why we updated to v12 (and not v8, v13 or v14). Then came the time to migrate our front end from Backbone to React. Until then I was relativly happy to remain on an older version. Yes, I know we were running a VERY old version, but our app was functioning without issue, and upgrading was a "nice to have", but not essential.Įventually we'd come to an upgrade (eg of our heroku stack) or of a dependency or new feature that would force us to upgrade. We ran node 4.5.0 for years without ever needing to advance to a more recent version. TLDR This short article deals with installing a later version of nodejs on a linux (ubuntu) Amazon EC2 instance.