ForgeWP

System Requirements

Everything you need installed on your computer before building themes with ForgeWP.

Before you start building with ForgeWP, your computer needs a few standard web development tools.

If you are new to programming, do not worry: you only need two core tools installed on your computer to start authoring themes today.

The Two Environments: Authoring vs Production

To understand what you need to install, it helps to separate the development environment (your computer where you write code) from the target WordPress environment (where your finished theme will eventually run):

Table · 3 columns
Environment
Purpose
What Is Needed
Development Environment (Your Laptop / PC)
Where you write React components, style layouts with Tailwind CSS, and run the ForgeWP compiler.
A dependency-compatible Node.js version (see below), a package manager, and a code editor. No database is required for the mock preview.
Target WordPress Environment (Local or Live Site)
Where you install and activate the compiled theme .zip archive to test it with live content.
WordPress 6.6+ for the generated theme.json v3, plus a PHP version supported by your WordPress release and installed plugins.
Do I need WordPress installed on my computer right now?

No. You can design and preview a theme without running Apache, MySQL, Docker, or LocalWP on your computer. ForgeWP includes a local CMS simulation layer (cms/) with mock posts, pages, and menus. Package installation and remote images or fonts may still need internet access.

1. Node.js

Node.js is an open-source JavaScript runtime that executes code outside of a web browser. ForgeWP uses Node.js behind the scenes to run the Vite dev server, parse your TypeScript components, and compile your theme into native WordPress PHP.

  • For the current compiler dependencies: use Node.js 22.18.0 or later in the 22.x line, or 24.11.0 or later in the 24.x line.
  • Declared support: ForgeWP packages and starter projects use ^22.18.0 || >=24.11.0, matching the Babel 8 dependency requirement. This excludes Node 23 and Node 24 releases below 24.11.0. Later stable major versions satisfy this range; use a supported Node release.
  • For another ForgeWP release: check its lockfile and dependency engine requirements. Use a supported Node.js release that satisfies the full toolchain.

How to Check Your Node.js Version

Open your terminal (PowerShell, Command Prompt, macOS Terminal, or Linux shell) and run:

Terminal
node -v

If Node.js is installed, you will see a version string similar to:

Terminal Output
v22.18.0

Check the complete version, including the numbers after the dots. For example, 22.17.0 does not meet a 22.18.0 minimum.

If the command is not recognized or the version does not meet the dependency requirements, install a compatible release from the official Node.js website, reopen the terminal, and check again. The CLI and forgewp doctor check the same version range as the package metadata.

2. Package Manager (pnpm Recommended)

A package manager downloads and manages the third-party libraries and tools your project relies on (such as React, Tailwind CSS, and Vite).

While ForgeWP works with npm, yarn, and bun, pnpm is strongly recommended. pnpm is significantly faster, saves gigabytes of disk space through hard linking, and prevents phantom dependency bugs.

How to Install and Verify pnpm

If you do not have pnpm installed, you can install it globally via npm (which comes bundled automatically with Node.js):

Terminal
npm install -g pnpm

Once installed, verify that it works:

Terminal
pnpm -v

You should see a version number like 9.1.0 or higher.

Using Other Package Managers

If your team or agency prefers standard npm, yarn, or bun, ForgeWP supports them as well. In the upcoming pages, we provide copy-and-paste commands for all four package managers.

3. Code Editor

You will need a code editor with solid support for TypeScript, JSX, and Tailwind CSS.

  • Recommended: Visual Studio Code (or forks like Cursor).
  • Recommended Extensions:
    • Tailwind CSS IntelliSense: Provides auto-completion and linting for Tailwind CSS classes.
    • Prettier: Formats your code automatically on save.
    • ESLint: Catches potential errors and syntax issues as you type.

4. Target WordPress Requirements (For Testing Exports)

When you are ready to compile your theme into a .zip archive and test it with live WordPress features, the target WordPress installation must meet these modern standards:

  • WordPress Version: 6.6 or higher. ForgeWP generates theme.json version 3, which WordPress supports starting with 6.6.
  • PHP Version: Use a version supported by your WordPress release and any plugins you plan to use. Choose a maintained PHP release offered by your host and verify the exported theme with your installed plugins. The generated PHP requirement defaults to 7.4 as metadata; raise it through compatibility.requiresPhp to match your project.
  • Theme Type: ForgeWP exports a PHP-backed hybrid theme. It generates PHP templates and uses theme.json for design settings and block-editor integration; this does not make the output a full block theme with Site Editor-managed HTML templates.

If you want to test the theme locally on your machine after exporting, popular free local WordPress tools include:

  • LocalWP (Easiest for beginners — spins up a full WordPress site in one click).
  • Docker / wp-env (Great for advanced developers who prefer containerized workflows).
  • Any Staging Server (Kinsta, WP Engine, SiteGround, or any standard cPanel web host).

Ready for the Next Step?

Now that your machine has Node.js and a package manager ready, proceed to Create A New Theme to scaffold your first ForgeWP theme project in under two minutes!