Exercise 2: Confirming the Node Version and Turbopack — Possible Solution
====================================================================

CHECKING THE NODE VERSION
------------------------------
Running node --version prints the installed Node.js version, e.g.
v20.11.0. Per this chapter, Next.js 16 requires 20.9.0 or later - Node
18 is no longer supported at all. Any version reading 20.9.0 or higher
meets the minimum; anything on the Node 18.x line or earlier would need
upgrading before Next.js 16 will run.

FINDING THE TURBOPACK CONFIRMATION
------------------------------
Running npm run dev (which just runs next dev, per this chapter's own
scaffolded package.json) prints startup output that names Turbopack
directly - typically a line reading something like "Next.js 16.3.x
(Turbopack)" near the top of the terminal output, immediately after the
server starts. No --turbopack flag was passed anywhere in the command
that was run, which is exactly the point: per this chapter, Turbopack
is on by default in Next.js 16, not something that has to be requested.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly reads the installed Node version against the chapter's own
stated 20.9.0 minimum rather than just assuming it passes, and correctly
identifies the terminal's own explicit "(Turbopack)" confirmation as
evidence of the default-on behavior, rather than just asserting it must
be true because the chapter said so.