CI #5 - Why use the setup-node action?

~~~~~~

RESOURCES:

Playlist:

Repository:

Github Actions Docs:

~~~~~~

00:00 - Introduction to setup-node
04:20 - Example proof of Node being preinstalled by default
06:17 - Adding setup-node
07:20 - Specifying node version for our actions
08:53 - Summary of why to use setup-node

~~~~~~

Follow Jimmy Cleveland's doings:

#ci #javascript

[SimonDoty-ss]

on the question of what node version is used and how it is determined -- are you sure windows 2016 had any Node version installed?

you seemed to jump to the conclusion that because the action runner defaulted to the LTS version when you specified windows 2016, it would behave the same for other OSes.
if you had selected an OS that actually came with Node, say Node 12, then printed node -v and it was in fact 14.17.0 (LTS at the time) that would tell you something.

the action runner defaulting to LTS because it was not installed on the OS you chose makes more sense than assuming the action runner will always determine the node version.