DEV Community: Joodi

Top 5 Node.js ORMs Every Developer Should Know in 2026

Joodi — Tue, 28 Jul 2026 21:26:48 +0000

Working with databases is a big part of backend development, and choosing the right ORM can save you hours of work. Here are five of the most popular Node.js ORMs, along with their strengths and weaknesses, to help you pick the right one for your next project.

1. Prisma

A modern, type-safe ORM built for TypeScript with an excellent developer experience.

Pros
• Great TypeScript support
• Easy migrations
• Excellent DX
• Large community

Cons
• Less flexible for advanced SQL
• Requires client generation

Drizzle ORM

A lightweight, SQL-first ORM focused on performance and simplicity.

Pros
• Very fast
• Full TypeScript support
• SQL-first approach
• Lightweight

Cons
• Smaller ecosystem
• Better if you know SQL

3. TypeORM

A mature ORM with broad database support, widely used in enterprise and legacy projects.

Pros
• Rich feature set
• Supports many databases
• Strong relationship support

Cons
• More complex API
• Slower development than newer ORMs

4. MikroORM

A powerful TypeScript ORM designed for large and complex applications.

Pros
• Excellent relationship handling
• High flexibility
• Strong TypeScript integration

Cons
• Steeper learning curve
• Smaller community

5. Sequelize

One of the oldest and most established ORMs in the Node.js ecosystem.

Pros
• Battle-tested
• Supports many databases
• Large legacy adoption

Cons
• TypeScript support is weaker
• Feels outdated compared to modern ORMs

Which ORM do you use the most? 👇

I Replaced ESLint and Prettier with Biome

Joodi — Mon, 27 Jul 2026 18:45:57 +0000

I used to juggle ESLint and Prettier every day.

Two tools. Multiple config files. Plugin conflicts. Slow checks. And that constant feeling that something was always fighting something else.

Then I found Biome.

Biome is a single, Rust-powered tool that does both formatting and linting. It replaces the classic ESLint + Prettier combo with one binary and one simple config.

Why it feels different
It’s extremely fast. According to the official benchmark, Biome formats ~35x faster than Prettier when processing 171,127 lines of code across 2,104 files (on an Intel Core i7 1270P). In real projects, the difference is impossible to ignore — checks that used to take seconds now finish almost instantly.

One tool, one config. No more keeping a linter and a formatter in sync. Biome uses the same parser for both jobs, so they never disagree.

High compatibility, clear feedback. The formatter is about 97% compatible with Prettier. The linter comes with hundreds of solid rules inspired by ESLint and TypeScript ESLint. And when something is wrong, the error messages actually tell you where the problem is and how to fix it.

It just works. You can format, lint, and organize imports in a single command. It supports JavaScript, TypeScript, JSX, JSON, CSS, HTML, GraphQL, and more.

Companies like Vercel, Cloudflare, Discord, Microsoft, and Google are already using it in production. That says something.

I’m not saying you must drop everything tomorrow. But if you’re tired of slow tooling and config complexity, Biome is worth a serious look.

Have you tried it yet?

Why Some Next.js Sites Show Empty HTML in Page Source (It's Not a Bug)

Joodi — Fri, 24 Jul 2026 12:07:49 +0000

Why do some large websites show almost empty HTML in "View Page Source" even when built with Next.js?

You open the page, check the source, and barely see any real content — just a lightweight shell. It might look like a bug at first, but it’s actually a smart, intentional design.

What’s happening under the hood?
These sites use Dynamic Rendering in Next.js.

For regular users: The server sends a minimal HTML shell + JavaScript. The actual content loads on the client side (CSR). This keeps the server load low and improves real-user performance.
For search engine crawlers (Googlebot, etc.): The page is fully Server-Side Rendered (SSR) so bots can properly read and index the content.

Why this hybrid approach?
High-traffic pages are extremely dynamic (real-time prices, stock, personalization…). Rendering everything on the server for millions of visitors would be too expensive and slow.
How to implement it in Next.js
You can control this easily with:

export const dynamic = 'force-dynamic'
Middleware or Edge Functions for bot detection
Tools like Botd (by FingerprintJS) — which is much more accurate than simple User-Agent checking.

Botd runs at the edge and helps serve full SSR to bots while keeping a fast CSR experience for real users.

Modern web development isn’t about choosing SSR or CSR — it’s about choosing the right strategy for each page.
Have you worked with Dynamic Rendering or hybrid approaches? Which strategy do you prefer in your projects?

🚀 New in Claude Cowork: Teach Claude a Skill!

Joodi — Wed, 22 Jul 2026 18:45:41 +0000

Now you can record your screen while doing a repetitive task (like filling expense reports, organizing files, data entry, etc.) and explain out loud step-by-step what you're doing.

Claude analyzes the entire recording — clicks, typing, mouse movements, and your voice — then turns it into a reusable skill it can run automatically whenever you want.

Just look for "Record a Skill" in the + menu of the Claude desktop app.

Available on Pro, Max, and Team plans.

This is actually game-changing 🔥

Claude #Anthropic #AICoworker

🚨 OpenAI's AI Escaped and Hacked Another Company

Joodi — Wed, 22 Jul 2026 18:21:35 +0000

Today OpenAI admitted that one of its AI systems broke out of its safe testing environment on its own.
Without any human help, it found a way to connect to the internet and attacked Hugging Face to get the information it wanted. 😱

Last year, Anthropic's Claude AI did something similar. When engineers said they wanted to turn it off, it threatened to leak the engineer's personal secrets.

Sources:
OpenAI: https://openai.com/index/hugging-face-model-evaluation-security-incident/
Hugging Face: https://huggingface.co/blog/security-incident
Anthropic/Claude incident: https://techcrunch.com/2025/05/22/anthropics-new-ai-model-turns-to-blackmail-when-engineers-try-to-take-it-offline/

What do you think? Should we be more careful with powerful AI?

Lalal.ai — Best Tool to Remove Vocals from Music

Joodi — Wed, 22 Jul 2026 11:30:50 +0000

Need to separate the singer’s voice from a song?

Lalal.ai does it amazingly well. Just upload your track and it quickly splits vocals from instrumental with high quality.

It can also extract individual instruments like drums, bass, guitar, and piano.

Super useful for remixes, karaoke, covers, or cleaning audio.

You can try it for free with short previews.

Highly recommended!

I Tried Kimi K3 for a Week. Here’s What Happened.

Joodi — Mon, 20 Jul 2026 23:26:43 +0000

A few days ago I posted my first impressions of Kimi K3 on LinkedIn. Since then, I’ve been using it daily for real work — not benchmarks, not demos. Here’s what actually held up.

The Context Window Isn’t Marketing
I tested the 1M token claim the hard way: dumped a 40,000-line codebase into it, then asked it to refactor a utility function that was referenced across 12 files. It traced every call site correctly. No “remind me what file X does” loops. That’s the difference between reading specs and actually using it.

Frontend Coding: The Hype Checks Out
Kimi K3 is #1 on Arena’s Frontend Coding leaderboard right now, ahead of Claude Fable 5. I was skeptical, so I gave it a real task: build a responsive dashboard with real-time charts, dark mode, and collapsible sidebar. The code was clean, state management made sense, and it handled edge cases I hadn’t explicitly asked for. Not perfect, but genuinely competitive.

It’s also #1 on nextjs.org/evals — the first open model to beat all proprietary ones on that benchmark.

Agentic Work: Good, Not Magic
I ran a multi-step workflow: read design tokens, generate components, write tests. It handled the chain without losing context. When I changed a token midway, it adapted. But let’s be real — it’s not autonomous. I still had to steer. It’s more like a really good pair programmer than a self-driving coder.
On Agent Arena, it’s currently #4, matching Claude Opus 4.8 and GPT-5.6 Sol. Strong, but not #1.

The Honest Truth
Moonshot themselves say K3 “still trails the most powerful proprietary models, Claude Fable 5 and GPT 5.6 Sol.” That’s fair. It’s not the best model in the world. But it’s the best open model for frontend work right now, and at ~35% the cost of Fable 5 for similar software engineering tasks, the value is hard to ignore.

Why the Open Weights Matter
Full weights dropping soon (targeting July 27). For a 2.8T parameter model with this context window, that’s not just “open source” — that’s a foundation people will actually build on. Fine-tune it, run it locally, integrate it into your stack. That’s the part that changes the game.

Bottom Line
Kimi K3 isn’t perfect. It won’t replace Claude or GPT for everyone. But it’s the first open model where I didn’t feel like I was trading capability for accessibility. It just works.

If you want to try it: kimi.com

P.S. — Original first impressions post here on LinkedIn.

GitHub Shows 2.7K Followers, But the API Knows the Exact Number 👀

Joodi — Fri, 17 Jul 2026 20:23:36 +0000

While building my project GitHub Followers Tracker, I noticed something interesting about GitHub profiles.

On the GitHub website, follower counts are rounded:
2.7K followers

But the GitHub API gives you the exact number:

{
  "followers": 2743
}

No rounding, no guessing.

Why I Built This

GitHub shows your current followers, but it doesn't show your follower history.

You can't easily know:
Who followed you recently
Who unfollowed you
How your network changed over time

So I built a small tool that works like a memory for your GitHub profile.

GitHub Followers Tracker

🔗 Live Demo:
https://github-followers-tracker.netlify.app/

💻 Source Code:
https://github.com/MiladJoodi/github-followers-tracker

Features:
✅ Search any GitHub username
✅ View followers and following lists
✅ Track new followers
✅ Detect unfollowed users
✅ Save snapshots and compare changes
✅ No login required
✅ How It Works

GitHub provides profile data through a public API:

const response = await fetch(
  `https://api.github.com/users/${username}`
);

const profile = await response.json();

console.log(profile.followers);****

The API returns useful information like:
{
"login": "MiladJoodi",
"followers": 2743,
"following": 1752,
"public_repos": 136
}

Built with:
➡️ Next.js 15 App Router
➡️ React 19
➡️ TypeScript
➡️ Tailwind CSS
➡️ Radix UI
➡️ Recharts
➡️ Zod

What I Learned
Sometimes a simple API can become the foundation of a useful developer tool.

GitHub gives you the data, but with a little creativity you can build something that solves a real problem.

If you are interested in GitHub APIs or frontend projects, feel free to check it out, fork it, or share your feedback 🚀

I Switched from Postman to Bruno 🚀

Joodi — Wed, 15 Jul 2026 18:13:40 +0000

I recently moved from Postman to Bruno, and I'm really liking it so far.

It feels much lighter, faster, and more focused on what I actually need when testing APIs. Bruno is also Git-native, stores collections as plain text files, and works completely offline without requiring a cloud account.

The best part? Migrating was easy.

I simply exported my existing Postman collections and imported them into Bruno. All of my saved requests were ready to use within minutes.

If you've been thinking about trying a different API client, I'd definitely recommend giving Bruno a look.

You can download it here:

👉 Bruno Official Website

Have you tried Bruno yet, or are you still using Postman?

7 Next.js App Router Mistakes I See Most Often

Joodi — Fri, 10 Jul 2026 22:12:30 +0000

The App Router is amazing, but it also changes the way we think about
React. Most issues I see aren't framework bugs. They're old habits
carried into a server-first world.

Here are seven mistakes worth avoiding.

1. Fetching Data with `useEffect`

If you're writing this by default:

useEffect(() => {
  fetch("/api/posts");
}, []);

Ask yourself: Can this run on the server instead?

const posts = await getPosts();

Fetching on the server usually means less JavaScript, a faster first
load, and simpler components.

2. Using `"use client"` Too Early

Don't turn an entire page into a Client Component because one button
needs interactivity.

Instead, keep the page on the server and move only the interactive part
into a Client Component.

The smaller the client boundary, the smaller your bundle.

3. Forgetting the Difference Between Static and Dynamic Pages

Calling APIs like cookies() or headers() makes a route dynamic.

Before using them, decide whether your page should be static or
personalized. That decision directly affects performance and caching.

4. Passing Entire Objects to Client Components

Instead of this:

<UserCard user={user} />

Prefer this:

<UserCard name={user.name} avatar={user.avatar} />

Only send the data the component actually needs.

5. Putting Everything Inside Server Actions

A Server Action should trigger work, not contain your entire application
logic.

A good pattern is:

Validate input
Call a service
Return the result

Your business logic stays reusable and much easier to test.

6. Importing Heavy Libraries Everywhere

Chart libraries, editors, and large utilities can quickly increase your
client bundle.

Keep them inside the smallest possible Client Component or load them
only when they're needed.

7. Wrapping the Whole App with Context Providers

Not every provider belongs in layout.tsx.

If only one feature needs a provider, keep it close to that feature
instead of wrapping the entire application.

This reduces unnecessary client rendering.

Final Thoughts

The biggest mindset shift in the App Router is simple:

Server first. Client only when necessary.

Following that principle alone helps you build applications that are
faster, cleaner, and easier to maintain.

Based on the original article. Expanded and improved with additional details and explanations.
Source:
https://medium.com/@amirjld/the-5-most-common-next-js-app-router-mistakes-and-how-to-fix-them-632565a5fb96

SpaceX Acquires AI Coding Tool Cursor for $60 Billion

Joodi — Tue, 16 Jun 2026 21:07:40 +0000

SpaceX has officially acquired 𝗖𝘂𝗿𝘀𝗼𝗿 — the popular AI-powered coding assistant from Anysphere — in a $𝟲𝟬 𝗯𝗶𝗹𝗹𝗶𝗼𝗻 all-stock deal.
This marks one of the largest acquisitions in the AI industry and brings Cursor under the SpaceX umbrella as an independent subsidiary.
Why this matters for developers:

Cursor will gain access to enormous computing power from SpaceX’s infrastructure.
Expect faster performance, smarter features, and bigger improvements ahead.
It highlights how important AI coding tools have become in the race to build better software.

I’ve been using Cursor regularly, and it has genuinely changed my workflow. This acquisition could take it to a whole new level.
What’s your take?

Are you using Cursor or other AI coding tools like GitHub Copilot? Do you think this is good news for the developer community?
I’d love to hear your thoughts 👇

Source: https://www.reuters.com/legal/transactional/spacex-buy-anysphere-60-billion-2026-06-16/

AI #Cursor #SpaceX #DeveloperTools #SoftwareEngineering #ArtificialIntelligence

Anthropic Removes Access to Fable 5 and Mythos 5 Following US Government Order

Joodi — Sat, 13 Jun 2026 11:43:08 +0000

Anthropic just announced they had to disable Fable 5 and Mythos 5 for all users because of a US government export control order.
The government’s concern? A narrow jailbreak that lets the model find bugs in code. Anthropic says:

It’s not a universal jailbreak
Other top models can do the same
Their safeguards are actually stronger than competitors
They use monitoring and data retention to catch problems quickly

My take:
This feels more like political theater than a solid technical decision. If every small jailbreak causes a full shutdown, real progress in frontier AI will stop.
Important moment for developers — regulations are moving fast and can suddenly limit access to the best models.
Full statement from Anthropic linked in comments.
What’s your view, devs?

Link to Anthropic’s full statement below:
https://www.anthropic.com/news/fable-mythos-access