How to Install Node.js 24 on Mac? 2026 Beginner Tutorial

Install Node.js 24 LTS from the official Node.js download page, then check node and npm in Terminal and run a small JavaScript file. If your course names another version, follow that requirement before changing your setup; the official release table lists Node.js 24 as LTS and Node.js 26 as Current as of September 26, 2026 (release status).

This guide is for students setting up Node.js on a Mac for the first time, or checking whether a course project can run.
It also covers school-managed Macs, where installation may be restricted.
If you already have a project but commands fail, use the checks below before changing system settings.

SECTION 01What Node.js and npm do in your course setup

Think of Node.js as a tool in your programming toolbox: it runs JavaScript files on your computer. npm is the package manager that comes with the Node.js toolchain. It helps a project work with the packages it needs; it is not another code editor. The npm documentation explains what npm does.

For a class assignment, the project folder is like the folder holding your homework. Node.js runs a file from that location, while npm may be used by the project to manage packages. VS Code is where you edit the file. These tools have separate jobs, so installing VS Code by itself does not install Node.js, and installing Node.js does not open or run your course project automatically.

Node.js 24 is a reasonable starting choice when the course does not specify a release: it is listed as LTS in the official release table. LTS is the release track to consider for a new setup when you want a supported version rather than automatically choosing the newest Current release. A course may depend on a different version, however, so its instructions take priority.

If your course provides a starter project, check its setup instructions before installing or upgrading. A project’s required version matters more than choosing a newer release.

SECTION 02Choose an installation route that fits your Mac

For a Mac you’re allowed to manage, start at the official Node.js download page. Select the macOS option that matches the Mac and follow the instructions provided there. Don’t download an installer from an unfamiliar site or follow an old video’s saved link without checking it against the current official page.

If the device is managed by your school, first check whether you’re permitted to install software. A blocked installer does not mean you should change protected settings, use someone else’s administrator password, or try to defeat device controls. Ask the school or course staff for an approved environment instead.

Before you begin, compare your situation with these options:

The installer and supported platform options can change, so use the current Node.js download information rather than relying on a copied path or an old set of screenshots. The official npm documentation also describes how its versioning works; don’t assume that a project’s npm requirement is identical to its Node.js requirement (npm version documentation).

SECTION 03Install Node.js 24 and confirm the commands

Use this sequence on a Mac where you’re allowed to install software:

1. Open the official Node.js download page and confirm that the release you intend to use is Node.js 24 LTS.
2. Choose the macOS download option shown for your Mac, then follow the official installation instructions.
3. When the installer finishes, close and reopen Terminal. This gives the new Terminal session a chance to load the installed command environment.
4. In Terminal, run node -v. The command should print the installed Node.js version. Compare it with your course requirement; don’t treat any version response as proof that it matches the assignment.
5. Run npm -v separately. npm has its own version output, so check it independently rather than assuming it works because node does.
6. Create a small file named hello.js in a folder you can find. Put console.log("Hello, JavaScript!"); in the file, save it, and use Terminal to run node hello.js from that folder.

The Node.js command-line examples show Node.js being run from a terminal with a JavaScript file. For your first check, you’re looking for the text printed by your file. If the version commands return values and the file prints the expected message, the basic runtime is available. You still need to confirm that the project uses the version and setup required by your course.

Do not copy an expected version number from a screenshot as if it were a universal answer. Your local output tells you what is installed now; your course materials tell you what the assignment expects. If those differ, pause before upgrading or replacing anything.

SECTION 04Diagnose a failed command before reinstalling

Start with the exact result shown in Terminal. A message saying that node cannot be found is different from a version appearing successfully, and both are different from a JavaScript error after a file begins running.

If a command is missing, close and reopen Terminal once, then run the same check again. If it still fails, return to the official Node.js download and installation page and review the route you used. Don’t delete folders, edit shell startup files, or run commands copied from a forum unless you understand what they change and have a course-approved reason to do so.

For a school-managed Mac, stop before attempting to adjust protected settings. Ask the administrator or instructor to confirm which installation methods are permitted. A restricted device is a policy question as well as a technical one.

SECTION 05Common questions from first-time learners

How can I check whether Node.js and npm are ready?

Open Terminal and run node -v and npm -v separately. Each command should print a version rather than an error. Then run a small JavaScript file with Node.js and check that its output appears. A version response confirms that the command is available; running the course project is the better check that the whole setup meets your class requirements.

Why can’t Terminal find node after installation?

Close and reopen Terminal, then try node -v again. If it still fails, the installation may not have completed, or the shell may not be finding the installed executable. Avoid changing shell files or deleting folders based on a guess. Check the official download instructions, and ask your school administrator for help if the Mac is managed.

What if my school computer doesn’t allow software installation?

Don’t bypass management settings or install software without permission. Ask whether the course provides a browser-based workspace, lab computer, or approved remote Mac. Before working, confirm that the files, editor, and Terminal are all connected to the same environment; otherwise, you may edit one copy of a project and run another.

SECTION 06Run a first file in VS Code

VS Code handles editing; Node.js runs the JavaScript file. Install the editor using its official macOS instructions, then open the folder where you saved hello.js. The VS Code documentation on additional components provides details about components and runtime tools.

Use VS Code’s integrated Terminal for your first check. Confirm that you opened the folder containing the file, then run node hello.js. You should see the message printed by the file in the Terminal. If Terminal reports that the file cannot be found, don’t reinstall Node.js first: check whether VS Code opened the right folder and whether the Terminal is running from that folder.

A useful first-run checklist is:

• The file is saved with the name hello.js.
• VS Code has the folder containing that file open.
• The integrated Terminal is using that project folder.
• node -v and npm -v return version information.
• Running node hello.js prints the message you put in the file.

If your class starter project includes setup instructions, follow those before trying extra packages or changing files. A simple file that runs successfully proves the basic connection between the editor, folder, and runtime; it does not prove that every project dependency is installed.

SECTION 07Keep the course project and runtime aligned

“Installed” and “ready for this assignment” are different checks. A Mac can have Node.js and npm available while a project still expects a different Node.js version or additional setup steps. Before changing your environment, read the course notes and any instructions included with the project.

If a project needs a version other than Node.js 24, don’t install or remove releases at random. Ask the instructor which version is expected and whether you should use an isolated environment. That keeps you from turning a working course setup into a harder-to-diagnose problem.

For a school computer that can’t run the project locally, ask which approved alternative the class supports. A browser workspace or school lab may be enough. A remote Mac can also help when the course specifically needs a Mac environment, but you’ll need to confirm that the project files and Terminal session are on that remote machine—not a different computer.

SECTION 08Decide what to do next

If you have a Mac that permits installation and your course doesn’t name a different release, use the official Node.js 24 LTS route, verify both commands, and run the small file before moving on. If the course sets a version, follow it. If the device blocks installation, stay within school policy and ask for an approved alternative.

For a standard JavaScript class, a working local setup is usually the simplest choice; renting a Mac won’t fix a project-version mismatch or replace the need to follow course instructions. But relying on a managed school computer can mean restricted installs, limited access outside school, and files split across different environments. If your course needs a Mac and your current device cannot provide an approved setup, compare the terms on the MACNOX pricing page and review the MACNOX remote Mac options before deciding whether temporary access fits your course. Make sure you can connect to the same machine where your files and Terminal session will live.

SECTION 09FAQ