DEV Community: Saurabh Sharma

code-review-graph vs Graphify vs codebase-memory-mcp: The Best Code Intelligence MCP Tools for AI Coding Agents (2026)

Saurabh Sharma — Thu, 02 Jul 2026 11:02:08 +0000

If you've spent real time pairing with Claude Code, Cursor, or Codex on a mid-to-large repository, you've probably hit the same wall I did: the agent keeps re-reading files it already saw an hour ago, burns half your context window on a routine PR review, and still misses the one caller three modules away that actually breaks. That's not a prompting problem - it's an architecture problem. LLMs are stateless, and grep-based exploration doesn't scale past a few hundred files.

Over the last few months, a new category of tooling has emerged to fix exactly this: local, persistent code knowledge graphs exposed over the Model Context Protocol (MCP). Instead of your AI assistant re-reading the whole repo on every task, these tools parse your codebase once with Tree-sitter (and sometimes LSP-grade type resolution), store it as a queryable graph, and hand your agent a structural map - callers, dependents, blast radius, architecture - in a single tool call.

I dug into three of the most relevant open-source projects in this space: code-review-graph, Graphify, and codebase-memory-mcp - GitHub stars, architecture differences, benchmark numbers, and which one actually fits your stack.

Why This Matters

Every one of these tools solves the same underlying problem in a slightly different way: an AI coding agent asked "what calls ProcessOrder?" or "what's the blast radius of this change?" shouldn't have to grep-and-read its way through your entire repository. A pre-built graph of functions, classes, imports, and call chains answers that in a single, cheap query instead of dozens of expensive file reads.

The payoff shows up directly in your API bill and your context budget - for a React/Node monorepo doing daily PR reviews, that's the difference between a review that costs a few thousand tokens and one that quietly eats your whole context window.

Quick Comparison

	code-review-graph	Graphify	codebase-memory-mcp
GitHub Stars	~16k ⭐	~75.2k ⭐	~22k ⭐
Forks	1.8k	7.5k	1.6k
Primary Language	Python	Python	C (pure, zero deps)
License	MIT	MIT	MIT
Install	`pip install code-review-graph`	`uv tool install graphifyy`	Single static binary (curl installer)
Language Coverage	24 languages + Jupyter	36 tree-sitter grammars + docs/PDF/images/video	158 languages (vendored grammars)
Core Differentiator	Blast-radius analysis for PR review	Multi-modal graph (code + docs + papers + meetings)	Hybrid LSP-grade type resolution, extreme indexing speed
Token Reduction (claimed)	8.2x average (up to 49x on monorepos)	~71.5x reported by third-party benchmark	~120x (99.2% reduction)
MCP Tools Exposed	28	Served via `python -m graphify.serve`	14
Backed By	Independent maintainer	Y Combinator (S26 batch)	DeusData

(Star counts move fast in this category - check each repo live before you quote them elsewhere.)

code-review-graph

GitHub: tirth8205/code-review-graph - ~16k ⭐, 1.8k forks, MIT

The most review-focused of the three. It builds a structural map of your code with Tree-sitter, storing nodes (functions, classes, imports) and edges (calls, inheritance, test coverage) in a local SQLite database under .code-review-graph/. Its signature feature is blast-radius analysis: when a file changes, the graph traces every caller, dependent, and test that could be affected, so your AI assistant reviews only the files that actually matter instead of the whole diff's neighborhood.

For React/Node developers specifically:

One command (code-review-graph install) auto-detects and configures Claude Code, Cursor, Codex, Windsurf, Zed, GitHub Copilot, and more.
Covers the full JS/TS stack - JavaScript, TypeScript, TSX, Vue, Svelte - alongside Python, Go, Rust, Java, and 24 languages total.
On a 27,700+ file Next.js monorepo, the graph funneled review context down to roughly 15 files.
Ships 28 MCP tools, including hub/bridge detection (architectural chokepoints) and auto-generated review questions - useful for onboarding onto an unfamiliar codebase, not just reviewing diffs.

Worth knowing before install: the project's own benchmarks are honest about limits - small single-file changes can see structural metadata exceed a raw file read, and flow detection currently favors Python frameworks over JS/Go.

pip install code-review-graph
code-review-graph install
code-review-graph build

Graphify

GitHub: safishamsi/graphify — ~75.2k ⭐, 7.5k forks, MIT, Y Combinator S26

The biggest project of the three by a wide margin, and it plays a different game. Where the other two are scoped to "index my code," Graphify's pitch is any input, one graph: point it at a folder and it pulls source code (36 tree-sitter grammars), SQL schemas, Terraform/HCL, Markdown, PDFs, Office docs, and even video/meeting transcripts into a single queryable NetworkX graph with Leiden community clustering.

What stands out:

Invoked as a slash command (/graphify .) inside 20+ AI coding assistants — Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Kilo Code, Aider — rather than requiring a persistent server.
Output is genuinely inspectable: graph.html (interactive visualization), GRAPH_REPORT.md (god-nodes, cross-module connections, suggested questions), and graph.json.
Supports pushing to Neo4j or FalkorDB, exporting Obsidian vaults, and a global cross-project graph for multi-repo orgs.
Also exposes an MCP server for teams who want persistent tool-call access instead of the slash-command flow.

Trade-off: the sheer surface area means non-code extraction depends on an LLM API call for semantic relationships — code-only graphs are fully local and free, but docs/PDFs/images route through your assistant's model API unless you point it at a local Ollama backend.

uv tool install graphifyy
graphify install
# then inside your AI assistant:
/graphify .

codebase-memory-mcp

GitHub: DeusData/codebase-memory-mcp — ~22k ⭐, 1.6k forks, MIT

The odd one out architecturally, in a good way: written in pure C, ships as a single static binary with zero runtime dependencies, and built for raw indexing speed. The headline number is stark - it indexed the Linux kernel (28M LOC, 75,000 files) in about 3 minutes, producing 4.81M nodes and 7.72M edges, with sub-millisecond query latency afterward.

What sets it apart:

158 vendored tree-sitter grammars compiled directly into the binary - nothing to install, nothing that breaks on a fresh machine.
Hybrid LSP semantic type resolution for Python, TypeScript/JavaScript/JSX/TSX, PHP, C#, Go, C/C++, Java, Kotlin, and Rust - refines call edges with actual type information rather than stopping at syntax.
Documented in a research preprint (arXiv:2603.27277), evaluated across 31 real-world repositories: 83% answer quality, 10x fewer tokens, 2.1x fewer tool calls versus file-by-file exploration.
Cross-service linking for backend/microservices teams - detects HTTP, gRPC, GraphQL, tRPC call sites, and pub-sub patterns across 8 languages.
A team-shared graph artifact can be committed to the repo so teammates skip a full reindex on clone.
Every release is SLSA Level 3 attested and Sigstore-signed - a level of supply-chain rigor the other two don't advertise.

Trade-off: no built-in LLM - it's a structural backend that relies entirely on your MCP client to translate natural language into graph queries, and Windows support currently needs WSL2 for building from source.

curl -fsSL https://raw.githubusercontent.com/DeusData/codebase-memory-mcp/main/install.sh | bash
# then in your agent:
"Index this project"

Head-to-Head

Token efficiency: all three publish impressive numbers, but they're measuring slightly different things. code-review-graph's 8.2x is an average including worst cases (small diffs can dip below 1x); Graphify's ~71.5x and codebase-memory-mcp's ~120x are best-case structural queries against an already-built graph. Treat them as directionally useful, not directly comparable.

Language coverage: if your stack is primarily JavaScript/TypeScript/React/Node, all three cover it well, but codebase-memory-mcp's Hybrid LSP layer gives noticeably richer type resolution for TS/JSX than pure Tree-sitter parsing alone. Graphify wins if your repo also includes Terraform, SQL schemas, or architecture docs you want in the same graph as the code.

Architecture philosophy: code-review-graph optimizes for the PR review loop specifically. Graphify optimizes for breadth of input (code + everything else). codebase-memory-mcp optimizes for raw performance and correctness at scale.

Best of the Best - Which One Should You Actually Install

Heavy PR review on a React/Node/TypeScript monorepo → code-review-graph. The blast-radius model and monorepo funnel are purpose-built for this, and install auto-detects Cursor/Claude Code/Copilot with no manual config.
One graph spanning code, architecture docs, RFCs, and meeting notes → Graphify. Multi-modal ingestion and Obsidian/Neo4j export are unmatched among the three.
Large, polyglot, performance-sensitive codebase (microservices, enterprise monorepo) → codebase-memory-mcp. Zero dependencies, sub-millisecond queries, and Hybrid LSP-grade accuracy make it the most "production infrastructure" feeling of the three.

They're not mutually exclusive - several teams run code-review-graph for the PR workflow and codebase-memory-mcp as the always-on structural backend, since neither one gatekeeps the other's MCP tools.

Other Similar Tools Worth Knowing About

Sourcegraph Cody - commercial code-intelligence and search platform, more IDE/enterprise-oriented than a pure MCP server.
Aider's repo map - a lighter-weight, built-in Tree-sitter-based repo summarization feature inside the Aider CLI.
Cursor's built-in codebase indexing - proprietary, cloud-assisted embedding index baked into the Cursor IDE, convenient but not portable across other agents.
GitHub Copilot workspace context - GitHub's own evolving context system for Copilot, tightly coupled to the GitHub ecosystem.

FAQ

Are these tools free and open-source?
Yes - all three are MIT-licensed. Graphify's parent, graphifylabs.ai, layers an optional paid enterprise tier (unlimited scale, team graphs, SSO) on top of the open-source core; the other two have no paid tier as of writing.

Do these tools send my code to the cloud?
All three are local-first for code parsing - Tree-sitter/AST extraction runs on your machine, no API calls. Graphify's non-code ingestion (docs, PDFs, images, video) does route through your configured LLM backend unless you point it at a local Ollama instance.

Which works best with Claude Code specifically?
All three ship first-class Claude Code integration. code-review-graph and codebase-memory-mcp both install hooks that nudge Claude Code toward graph queries instead of Grep/Glob; Graphify uses a /graphify slash-command plus an optional MCP server.

Do I need to pick just one?
No - they expose different MCP tool names and don't conflict.

Final Verdict

If you're optimizing an AI-assisted workflow around a JavaScript/React/Node stack, my honest recommendation is to start with code-review-graph for the PR review loop, and evaluate codebase-memory-mcp if you outgrow it on a larger, more polyglot codebase where indexing speed and type-aware resolution start to matter. Graphify earns its spot if your team's real pain point is scattered documentation and tribal knowledge, not just source code.

All three are moving fast, all three are MIT-licensed, and all three solve something generic RAG and grep-based context can't: giving your AI coding agent a persistent, structural memory of your codebase instead of making it rediscover your architecture every session.

Checkout Full Blog - https://www.saurabhsharma.dev/blogs/code-graph-mcp-tools-comparison

The Rise of GCCs in India: Why Global Companies Are Hiring Directly While Traditional IT Struggles

Saurabh Sharma — Fri, 26 Jun 2026 04:43:31 +0000

🚨 A silent shift is happening in India's tech industry.

While headlines focus on hiring freezes at traditional IT companies, another ecosystem is expanding rapidly.

Global Capability Centers (GCCs).

Over 2.5 million professionals are already working in GCCs across India, and new centers are opening every quarter.

So, what's different?

Traditional IT companies:

Build solutions for external clients
Bill by the hour or project
Clients own the product and IP

GCCs:

Are owned by global MNCs
Build the company's own products and platforms
Own the IP, engineering, and long-term innovation

Why are more companies choosing this model?

🤖 AI has changed the economics. Companies no longer need hundreds of engineers to justify setting up an India office. Smaller, highly productive AI-enabled teams make it viable.

🌍 India has become a global engineering hub. World-class talent, mature tech ecosystems, and cost efficiency make India an obvious choice for long-term investment.

The result?

📈 GCCs continue expanding.
💰 Many offer 20–25% higher compensation than traditional IT services.
🚀 Engineers get more opportunities to work on core products instead of outsourced projects.

This isn't the end of India's IT services industry.

But it is a signal that the future of software engineering is evolving—from service delivery to product ownership, AI, and innovation.

I explored this shift in detail, including why it matters for software engineers planning their careers.

📖 Read the full article here:
👉 https://www.saurabhsharma.dev/blogs/rise-of-gccs-india-ai-jobs

Do you think GCCs will become the preferred career destination for software engineers over traditional IT companies?

Is FAANG Becoming MANGO in the AI Era?

Saurabh Sharma — Tue, 16 Jun 2026 06:13:21 +0000

Is FAANG Becoming MANGO in the AI Era?

For years, FAANG was the gold standard for innovation and engineering excellence.

If you were a developer, working at companies like Facebook (Meta), Apple, Amazon, Netflix, or Google was often seen as the ultimate career goal.

But the AI revolution is changing the conversation.

Today, some of the most influential companies aren't just building products—they're building intelligence. The spotlight is increasingly shifting toward AI-native organizations such as OpenAI, Anthropic, NVIDIA, and others that are shaping the future of software.

The Bigger Shift

This isn't really about replacing FAANG with another acronym.

It's about a fundamental shift in technology:

Search → Answers
Automation → Agents
Software → Intelligence
Features → Capabilities

As developers, we're entering an era where understanding AI is becoming as important as understanding frameworks, databases, and system design.

What This Means for Engineers

The most valuable engineers of the next decade will likely combine:

Strong software engineering fundamentals
AI-assisted development skills
Prompt engineering
LLM and agent integration
AI-powered product thinking

The goal isn't to compete with AI.

The goal is to learn how to build with it.

Read the Full Article

This post was inspired by a thought-provoking article that explores the FAANG-to-MANGO idea in much greater detail.

👉 Read the complete article here:
https://www.saurabhsharma.dev/blogs/mangos-vs-faang-ai-era/

What do you think?

Are we witnessing the rise of a new generation of AI-first companies, or will traditional tech giants continue to lead the next wave of innovation?

Deploy Angular 16/17/18/19 on cPanel - The Version-Specific Guide ⚡

Saurabh Sharma — Wed, 13 May 2026 06:13:30 +0000

Most Angular deployment guides are written for one version, then quietly become outdated. You follow the steps, something breaks, and you have no idea why — because the guide was for Angular 17 and you're on Angular 19.

This guide is split by version. Find your path. Follow only that section.

Full deep-dive with all details at saurabhsharma.dev

Step 0 — Check Your Angular & Node.js Versions First

sh ng version node --version

Note the Angular version number. You'll need it to pick the right path below.

Step 1 — Node.js Compatibility (Read Before Building)

Your local Node.js must match what's available on your cPanel server. Mismatches silently fail npm install on the server.

| Angular Version | Minimum Node.js | Recommended | |---|---|---| | Angular 16 | 16.14.x | 18.x LTS | | Angular 17 | 18.13.x | 18.x or 20.x LTS | | Angular 18 | 18.19.x | 20.x LTS | | Angular 19 | 20.11.x | 20.x or 22.x LTS |

Check what your cPanel supports:
cPanel → Setup Node.js App → + CREATE APPLICATION → Node.js version dropdown.

Mismatch? Use nvm to switch locally:

nvm install 20
nvm use 20
node --version  # confirm

Choose Your Path

Does your project use SSR?
│
├─ NO  → Path A — CSR (all versions)
│
└─ YES → Which version?
         ├─ Angular 16  → Path B
         ├─ Angular 17/18 → Path C
         └─ Angular 19  → Path D

How to check if your project uses SSR:

grep -E '"@angular/ssr|@nguniversal' package.json

Line returned = SSR. Nothing = CSR.

Path A — CSR (Static) — All Angular Versions

No Node.js server needed. Just static files + .htaccess.

1. Build

ng build

Important — the output folder changed in Angular 17:

# Angular 16 and below — upload from here:
dist/your-app-name/

# Angular 17 and above — upload from HERE (the browser subfolder):
dist/your-app-name/browser/

Uploading the wrong folder = blank page with no obvious error.

2. Upload to cPanel

Upload the contents of your build folder (not the folder itself) to public_html/.

Via File Manager: Zip the folder → upload → right-click → Extract.

Do NOT upload: node_modules/, .git/, .env, source .ts files.

3. Create `.htaccess`

This is the step most people miss. Without it, every route except / returns 404.

In cPanel File Manager → Settings → enable Show Hidden Files → create .htaccess:

RewriteEngine On
RewriteBase /
RewriteRule ^index\.html$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-l
RewriteRule . /index.html [L]

App in a subfolder (e.g. yourdomain.com/myapp/)? Change RewriteBase / to RewriteBase /myapp/.

4. Test

Visit your domain. Then try a deep route like /about directly in the URL bar. If it loads — you're done.

✅ CSR deployment complete.

Path B — SSR: Angular 16 (Universal)

Angular 16 uses @nguniversal and needs a server.ts modification to work on Apache Passenger.

1. Modify `server.ts`

Replace this:

function run(): void {
  const port = process.env['PORT'] || 4000;
  const server = app();
  server.listen(port, () => {
    console.log(`Node Express server listening on http://localhost:${port}`);
  });
}

With this:

function isRunningOnApachePassenger(): boolean {
  return moduleFilename.includes('lsnode.js');
}

function run(): void {
  const server = app();

  if (isRunningOnApachePassenger()) {
    server.listen(() => {
      console.log('Node Express listening to Passenger Apache');
    });
    return;
  }

  const port = process.env['PORT'] || 4000;
  server.listen(port, () => {
    console.log(`Node Express server listening on http://localhost:${port}`);
  });
}

Also update the conditional at the bottom of the file:

// Before
if (
  moduleFilename === __filename ||
  moduleFilename.includes('iisnode')
)

// After
if (
  moduleFilename === __filename ||
  moduleFilename.includes('iisnode') ||
  isRunningOnApachePassenger()
)

2. Build

npm run build:ssr

Output:

dist/your-app-name/
├── browser/
└── server/
    └── main.js   ← this is your startup file

3. Upload

Create a directory outside public_html/ — e.g. /home/username/my-angular-app/.

⚠️ SSR apps cannot run from public_html/ on Namecheap shared hosting. This is a cPanel/Passenger constraint.

Zip your project (excluding node_modules/, .git/, README.md, .gitignore), upload there, extract.

4. cPanel Node.js App Setup

Setup Node.js App → + CREATE APPLICATION:

Field	Value
Node.js version	Match your local (e.g. 18.x)
Application mode	Production
Application root	`/home/username/my-angular-app/`
Application URL	Your domain
Application startup file	`dist/your-app-name/server/main.js`

Then: Stop → Run NPM Install → Start App.

✅ Angular 16 SSR complete.

Path C — SSR: Angular 17 & 18

No server.ts changes needed. Build command is ng build. Startup file is server.mjs.

1. Build

ng build

Output:

dist/your-app-name/
├── browser/
└── server/
    └── server.mjs   ← startup file (NOT main.js)

2. Upload

Same as Path B — directory outside public_html/. Zip without node_modules/, upload, extract.

3. cPanel Node.js App Setup

Field	Value
Node.js version	18.x or 20.x
Application mode	Production
Application root	`/home/username/my-angular-app/`
Application URL	Your domain
Application startup file	`dist/your-app-name/server/server.mjs`

Then: Stop → Run NPM Install → Start App.

✅ Angular 17/18 SSR complete.

Path D — SSR: Angular 19

SSR is built-in. ES Modules by default. Same server.mjs startup file.

1. Add SSR (if not already set up)

ng add @angular/ssr

2. Add ES Module support to `package.json`

{
  "name": "my-angular-app",
  "version": "1.0.0",
  "type": "module",
  "scripts": {
    "build": "ng build",
    "serve:ssr": "node dist/my-angular-app/server/server.mjs"
  }
}

3. Build

ng build

Output:

dist/your-app-name/
├── browser/
│   ├── index.html
│   └── main.abc123.js
└── server/
    └── server.mjs

4. Upload

Directory outside public_html/. Zip, upload, extract.

5. cPanel Node.js App Setup

Field	Value
Node.js version	20.x or 22.x
Application mode	Production
Application root	`/home/username/my-angular-app/`
Application URL	Your domain
Application startup file	`dist/your-app-name/server/server.mjs`

Stop → Run NPM Install → Start App.

✅ Angular 19 SSR complete.

Startup File Quick Reference

The single most common cPanel mistake — pointing to the wrong file:

Angular Version	Startup File
Angular 16 (SSR)	`dist/your-app-name/server/main.js`
Angular 17 (SSR)	`dist/your-app-name/server/server.mjs`
Angular 18 (SSR)	`dist/your-app-name/server/server.mjs`
Angular 19 (SSR)	`dist/your-app-name/server/server.mjs`

Performance: `.htaccess` With Caching + Compression

RewriteEngine On
RewriteBase /
RewriteRule ^index\.html$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-l
RewriteRule . /index.html [L]

# GZIP compression
<IfModule mod_deflate.c>
  AddOutputFilterByType DEFLATE text/html text/plain text/css
  AddOutputFilterByType DEFLATE application/javascript application/json
</IfModule>

# Cache hashed JS/CSS forever
<FilesMatch "\.(js|css)$">
  Header set Cache-Control "public, max-age=31536000, immutable"
</FilesMatch>

# Cache images 1 year
<FilesMatch "\.(jpg|jpeg|png|gif|ico|svg|webp|woff2)$">
  Header set Cache-Control "public, max-age=31536000"
</FilesMatch>

# Always revalidate HTML
<FilesMatch "\.html$">
  Header set Cache-Control "public, max-age=3600, must-revalidate"
</FilesMatch>

Troubleshooting

404 on all routes except /
→ .htaccess missing. Go to File Manager → Settings → enable Show Hidden Files → create it.

App looks unstyled (no CSS/images)
→ Wrong baseHref in angular.json. Set "baseHref": "/" and rebuild.

cPanel shows "Application is down"
→ Check Detected Configuration Files in the Node.js App panel for error output. Common causes:

Wrong startup file path (check the table above)
Wrong Node.js version (stop → change → NPM Install → start)
Missing dependencies (stop → NPM Install → start)

npm install fails on server
→ Local Node.js doesn't match cPanel. Use nvm use 20 locally, rebuild, re-upload.

Routes break on page refresh (SSR)
→ Missing catch-all route in your server file:

app.get('*', (req, res) => {
  res.sendFile(join(__dirname, '../browser/index.html'));
});

app.server.module not found (Angular 16)
→ @nguniversal not installed:

npm install @nguniversal/express-engine
npm run build:ssr

Version Comparison

Feature	Angular 16	Angular 17	Angular 18	Angular 19
Min Node.js	16.14	18.13	18.19	20.11
SSR package	`@nguniversal`	`@angular/ssr`	`@angular/ssr`	Built-in
Build command	`npm run build:ssr`	`ng build`	`ng build`	`ng build`
Startup file	`server/main.js`	`server/server.mjs`	`server/server.mjs`	`server/server.mjs`
server.ts change needed	✅ Yes	❌ No	❌ No	❌ No
ES Modules default	❌ No	❌ No	Optional	✅ Yes

Pre-Launch Checklist

[ ] Local node --version matches cPanel
[ ] ng build completes with zero errors
[ ] Uploaded correct folder (browser/ for Angular 17+, root dist for Angular 16 CSR)
[ ] .htaccess in domain root (CSR deployments)
[ ] node_modules/ NOT uploaded — ran NPM Install in cPanel instead
[ ] Startup file path matches your version (see table above)
[ ] All routes work including direct URL access
[ ] Styles and images load
[ ] HTTPS enabled (free Let's Encrypt in cPanel)

Found this useful? The full guide with every detail, decision tree, FAQ, and subfolder configs is at saurabhsharma.dev.

Drop a comment with your Angular version and deployment type — happy to help debug.

DEV Community: Saurabh Sharma

code-review-graph vs Graphify vs codebase-memory-mcp: The Best Code Intelligence MCP Tools for AI Coding Agents (2026)

Why This Matters

Quick Comparison

code-review-graph

Graphify

codebase-memory-mcp

Head-to-Head

Best of the Best - Which One Should You Actually Install

Other Similar Tools Worth Knowing About

FAQ

Final Verdict

The Rise of GCCs in India: Why Global Companies Are Hiring Directly While Traditional IT Struggles

Is FAANG Becoming MANGO in the AI Era?

Is FAANG Becoming MANGO in the AI Era?

The Bigger Shift

What This Means for Engineers

Read the Full Article

Deploy Angular 16/17/18/19 on cPanel - The Version-Specific Guide ⚡

Choose Your Path

Path A — CSR (Static) — All Angular Versions

1. Build

2. Upload to cPanel

3. Create .htaccess

4. Test

Path B — SSR: Angular 16 (Universal)

1. Modify server.ts

2. Build

3. Upload

4. cPanel Node.js App Setup

Path C — SSR: Angular 17 & 18

1. Build

2. Upload

3. cPanel Node.js App Setup

Path D — SSR: Angular 19

1. Add SSR (if not already set up)

2. Add ES Module support to package.json

3. Build

4. Upload

5. cPanel Node.js App Setup

Startup File Quick Reference

Performance: .htaccess With Caching + Compression

Troubleshooting

Version Comparison

Pre-Launch Checklist

3. Create `.htaccess`

1. Modify `server.ts`

2. Add ES Module support to `package.json`

Performance: `.htaccess` With Caching + Compression