# What Version of Node.js Does Meetily Require?

> Discover the Node.js version Meetily requires. Learn about the specific Node.js 20 LTS requirement and compatible alternatives for smooth operation.

- Repository: [Zackriya Solutions/meetily](https://github.com/Zackriya-Solutions/meetily)
- Tags: requirements
- Published: 2026-07-08

---

**Meetily requires Node.js 20 (LTS) or higher for its frontend, as specified by the `@types/node` dependency in [`frontend/package.json`](https://github.com/Zackriya-Solutions/meetily/blob/main/frontend/package.json), though any current LTS release (≥18) will function correctly.**

Meetily is an open-source meeting assistant built by Zackriya-Solutions that combines a **Next.js 14** frontend with Rust-based backend components. To compile the TypeScript codebase and execute build scripts like [`frontend/scripts/tauri-auto.js`](https://github.com/Zackriya-Solutions/meetily/blob/main/frontend/scripts/tauri-auto.js), you need a modern Node.js runtime aligned with the project's type definitions.

## How Meetily Specifies Node.js Version Requirements

### The package.json Type Definition

The definitive source for Node.js version requirements is found in **[`frontend/package.json`](https://github.com/Zackriya-Solutions/meetily/blob/main/frontend/package.json)**. Within the `devDependencies` section, the project declares:

```json
"@types/node": "^20"

```

This dependency locks the TypeScript compiler to Node.js 20 APIs, ensuring that all **file system operations**, **path utilities**, and **crypto modules** used in the build pipeline match the Node 20 specification. When you run `pnpm install` or `npm install`, the type checker validates your code against Node 20 standards.

### Compatibility with Node.js 18 and 22

While the typings explicitly target Node 20, the Next.js 14 frontend remains compatible with any **current LTS release** (Node.js 18 or higher). However, using Node 20 eliminates type mismatch warnings and ensures full compatibility with the development environment as tested by the maintainers.

## Verifying Your Node.js Installation

Before cloning the repository, confirm your Node.js version meets the minimum requirement:

```bash
node --version

```

If the output shows `v20.x.x` or higher, your environment satisfies Meetily's runtime requirements.

## Installing Node.js 20 for Meetily Development

### Using Node Version Manager (nvm)

For Unix-like systems, install and switch to Node 20 using **nvm**:

```bash

# Install Node.js 20 LTS

nvm install 20

# Activate for current session

nvm use 20

# Verify

node --version  # Should output v20.x.x

```

### Manual Installation

Download the Node.js 20 LTS installer directly from nodejs.org if you are on Windows or prefer a system-wide installation package.

## Building the Meetily Frontend

Once Node 20 is active, navigate to the frontend directory to install dependencies and start the development server. The build process relies on Node.js to execute the Tauri integration scripts:

```bash
cd frontend

# Install dependencies (requires Node ≥18, tested on Node 20)

pnpm install

# Start the Next.js development server

pnpm run dev

```

According to the **[`frontend/README.md`](https://github.com/Zackriya-Solutions/meetily/blob/main/frontend/README.md)** in the *For Developers* section, both **Rust** and **Node.js** must be installed to build the project successfully. The [`frontend/scripts/tauri-auto.js`](https://github.com/Zackriya-Solutions/meetily/blob/main/frontend/scripts/tauri-auto.js) file executes Tauri commands via Node.js, requiring a recent runtime to handle the subprocess spawning and file watching operations correctly.

## Summary

- **Node.js 20** is the recommended version, enforced by `@types/node` in [`frontend/package.json`](https://github.com/Zackriya-Solutions/meetily/blob/main/frontend/package.json)
- Any **LTS version ≥18** will function, but Node 20 matches the project's type definitions
- The **[`frontend/scripts/tauri-auto.js`](https://github.com/Zackriya-Solutions/meetily/blob/main/frontend/scripts/tauri-auto.js)** script requires a modern Node runtime for Tauri integration
- Both **Rust** and **Node.js** are required to build the complete application per the frontend README

## Frequently Asked Questions

### Can I run Meetily with Node.js 18?

Yes. While the `@types/node` package targets version 20, Node.js 18 (the previous LTS) provides sufficient API compatibility to build and run the frontend. However, you may encounter TypeScript warnings if your code paths hit Node 20-specific features used in the build pipeline.

### Does Meetily work with Node.js 22?

Yes. Node.js 22 is a current LTS release that maintains backward compatibility with the Node 20 APIs specified in [`frontend/package.json`](https://github.com/Zackriya-Solutions/meetily/blob/main/frontend/package.json). The project should build and run correctly on Node 22, though the CI/CD pipelines may primarily test against Node 20.

### Where is the Node.js version specified in the Meetily repository?

The Node.js version requirement is explicitly defined in **[`frontend/package.json`](https://github.com/Zackriya-Solutions/meetily/blob/main/frontend/package.json)** through the `"@types/node": "^20"` devDependency. This file also lists the Next.js 14 framework and other TypeScript tooling that expects a modern Node runtime.

### Why does Meetily require Node.js if it uses Rust?

Meetily employs a hybrid architecture where the **backend core is Rust** (likely for Tauri desktop capabilities), while the **frontend is Next.js 14** (React/TypeScript). Node.js is required to compile the frontend assets, run the development server, and execute automation scripts like [`frontend/scripts/tauri-auto.js`](https://github.com/Zackriya-Solutions/meetily/blob/main/frontend/scripts/tauri-auto.js) that bridge the JavaScript and Rust environments.