2026 Fast Node.js Setup: A Developer's Guide

Let’s be honest: how many times have you started a new Node.js project only to waste 30 minutes fiddling with config files, outdated packages, or inconsistent tooling? In 2026, the Node.js ecosystem is faster, more opinionated, and more standardized — but only if you set it up right from the start. This guide cuts through the noise and gives you a lean, production-ready setup in under 5 minutes.

1. Use the Right Node Version (and Keep It Stable)

Node.js 22 is now the active LTS (Long-Term Support) version as of 2026. It’s stable, fast, and supported through 2026 (with security fixes into 2027). Don’t guess your version. Use a version manager.

# Use fnm (fast, written in Rust) — it's better than nvm in 2026
curl -fsSL https://fnm.vercel.app/install | bash

# Then install and use Node 22
fnm install 22
fnm use 22

Check it:

node -v  # Should output v22.x.x

Pro tip: Add engineStrict: true in package.json to prevent teammates from using the wrong version.

{
  "engines": {
    "node": ">=22.0.0"
  },
  "engineStrict": true
}

2. Initialize Your Project Like a Pro

Skip the defaults. Use --yes but customize key fields.

npm init --yes

Then immediately edit package.json:

{
  "name": "my-fast-service",
  "version": "0.1.0",
  "type": "module",  // Use ES modules by default in 2026
  "main": "src/index.js",
  "scripts": {
    "dev": "node --watch src/index.js",
    "start": "node src/index.js",
    "lint": "eslint src",
    "test": "vitest"
  },
  "keywords": [],
  "author": "",
  "license": "MIT"
}

Yes, "type": "module" — CommonJS is still around, but ESM is the default now. Get used to .js files behaving like modules.

3. Write Modern JavaScript (No Babel Needed)

In 2026, Node 22 supports top-level await, import/export, and most ES2025 features. You don’t need Babel for basic projects.

src/index.js:

const express = await import('express');

const app = express.default();
const PORT = process.env.PORT || 3000;

app.get('/', (req, res) => {
  res.json({ message: 'Fast setup, live in 2026' });
});

app.listen(PORT, () => {
  console.log(`🚀 Server running on http://localhost:${PORT}`);
});

Install express:

npm install express

Run it:

npm run dev

That --watch flag in the dev script? It’s built into Node 22+. No nodemon needed unless you need advanced restart logic.

4. Linting and Formatting: Minimal but Enforced

Use eslint with eslint-config-fast — a community preset that’s strict but not annoying.

npm install --save-dev eslint eslint-config-fast

.eslintrc.json:

{
  "extends": ["fast"]
}

No need to overthink rules. This config enforces:

• No var
• No console in production (via CI)
• Proper async/await usage
• Import order and spacing

Run with:

npm run lint

Pair it with prettier only if your team fights over formatting. But in 2026, most teams just use the fast defaults and move on.

5. Testing: Vitest is the Default Now

Jest is legacy. Vitest is faster, lighter, and built for ESM.

npm install --save-dev vitest

Add test script:

"scripts": {
  "test": "vitest",
  "test:watch": "vitest --watch"
}

Example test (src/index.test.js):

import { describe, it, expect } from 'vitest';
import { app } from './index.js';

// Mock request logic or extract handler for unit testing
// But for integration, you can do:
describe('GET /', () => {
  it('returns a welcome message', async () => {
    const res = await request(app).get('/');
    expect(res.statusCode).toBe(200);
    expect(res.body.message).toBe('Fast setup, live in 2026');
  });
});

You’ll also need supertest:

npm install --save-dev supertest

And import it at the top:

const request = (await import('supertest')).default;

Run tests:

npm test

6. Git and .gitignore: Don’t Skip This

Initialize git and use a modern .gitignore.

git init

.gitignore:

node_modules
.env
dist
coverage
*.log
.DS

---

☕ **Appreciative**