DEV Community: Ankesh Sharma

ESLint Flat Config (v9) Setup for TypeScript: A Clean, Scalable Guide

Ankesh Sharma — Sat, 02 May 2026 18:00:35 +0000

Intro

With the release of ESLint v9, flat config is now the standard.

But most TypeScript projects are still using outdated .eslintrc setups.

If you're searching for:

ESLint flat config TypeScript setup
ESLint v9 configuration guide
modern ESLint config example

This guide shows a clean, scalable approach that works in real projects.

Why ESLint flat config matters

Flat config isn’t just a syntax change.

It solves real problems:

simpler configuration structure
better performance
easier composition across projects
future-proof with ESLint v9+

If you're still using .eslintrc, you're working against the direction ESLint is moving.

Where to put the config

Create this file at the root of your project:

eslint.config.js

ESLint automatically detects this in v9.

Installation

npm install -D eslint @iamankeshsharma/eslint-config

Basic TypeScript setup (flat config)

// eslint.config.js

import config from "@iamankeshsharma/eslint-config";

export default config();

This gives you:

TypeScript support
import sorting
modern JavaScript best practices
Prettier compatibility

Project structure example

your-project/
├── src/
├── eslint.config.js
├── package.json
└── tsconfig.json

What this setup handles

TypeScript support

proper parsing
type-aware linting
consistent patterns

Code quality

catches subtle bugs early
prevents unsafe patterns
enforces modern syntax

Import organization

consistent ordering
cleaner diffs
better readability

Customization

// eslint.config.js

import config from "@iamankeshsharma/eslint-config";

export default config({
  rules: {
    "no-console": "warn",
  },
});

Running ESLint

Add script:

{
  "scripts": {
    "lint": "eslint ."
  }
}

Run:

npm run lint

Common mistakes with flat config

mixing .eslintrc with eslint.config.js
not placing config at project root
manually combining plugins incorrectly
ignoring TypeScript-specific rules

Why this scales better

In multi-project environments:

one shared config
consistent rules everywhere
faster onboarding
fewer PR discussions

Used across multiple projects to standardize code quality and reduce PR noise.

The key idea

Flat config makes ESLint composable.

That means you can treat linting as:

A system — not a per-project setup.

Try it

If you're setting up ESLint for TypeScript with flat config:

Check it here:
@iamankeshsharma/eslint-config

EsLint Config for Next.js

Final thought

The biggest benefit of modern ESLint setups isn’t stricter rules.

It’s removing inconsistency before it spreads.

Best ESLint Config for Next.js (TypeScript + Tailwind Setup Guide)

Ankesh Sharma — Thu, 30 Apr 2026 09:23:30 +0000

If you're using Next.js with TypeScript and Tailwind CSS, setting up ESLint correctly is harder than it should be.

Most guides either:

cover only basics
ignore Tailwind
or don’t scale for real projects

This guide gives you a complete, scalable ESLint setup for Next.js.

What we want from ESLint in Next.js

A good setup should:

support TypeScript
enforce React hooks rules
align with Next.js best practices
handle Tailwind CSS properly
scale across projects

Installation

npm install -D eslint@^9 @eslint/js typescript-eslint eslint-plugin-react eslint-plugin-react-hooks @next/eslint-plugin-next eslint-plugin-tailwindcss prettier prettier-plugin-tailwindcss

Minimal setup

import createNextConfig from "@iamankeshsharma/eslint-config/next";

export default createNextConfig();

Why this works better

Instead of manually combining multiple configs, this approach:

standardizes rules
reduces setup complexity
avoids config conflicts
works with ESLint v9 flat config

Tailwind support

"tailwindcss/classnames-order": "warn",
"tailwindcss/no-contradicting-classname": "error"

This improves:

readability
consistency
maintainability

Common mistakes

mixing old .eslintrc with flat config
ignoring Tailwind linting
disabling rules instead of fixing structure

Final setup

import createNextConfig from "@iamankeshsharma/eslint-config/next";

export default createNextConfig();

Try it

If you want a production-ready setup:

@iamankeshsharma/eslint-config

Created a PRD for My Task Tracker Project (Focused on OSS Devs)

Ankesh Sharma — Thu, 19 Mar 2026 11:39:18 +0000

Hey devs,

I’ve been working on a Task Tracker / Project Management Tool, and this time I started with a PRD before coding to get more clarity.

What this project is about
It’s a tool designed for individual developers and OSS contributors who struggle to track:

GitHub Issues
Pull Requests
Todos across multiple repos

All in one place.

Problem I’m trying to solve
Right now, there are very limited options that centralize OSS work (PRs, issues, tasks) into a single dashboard. Most tools are either too heavy or not focused on individual workflows.

Core idea

GitHub-based authentication
Fetch PRs, issues, and tasks across repos
Unified dashboard for tracking everything
Individual mode + Team mode
Email reminders for deadlines (must-have)

Key Features

Project Board (Kanban + Table view)
Custom columns (todo, in-progress, done, etc.)
Task detail panel with markdown support
Timeline view (like git history of work)
GitHub issue-based tracking
Email notifications/reminders

Tech Stack

Frontend: React + Tailwind (Vercel)
Backend: Node.js + Express (Render)
Auth: Firebase + GitHub OAuth
DB: MongoDB Atlas
Email: SendGrid

Goals

Simple UI, better-than-average UX
Centralized task visibility
Build something useful (and actually used)
Learn while building

Known Risks

Email limitations (especially Gmail domain restrictions)
Dependency on SendGrid free tier

I’ve shared the full PRD here:
iamankeshsharma/Task-Tracker

Would really appreciate your feedback on:

Feature scope (too much / too little?)
Missing use cases
UX flow improvements
OSS-specific needs I might’ve missed

Let’s build something useful for developers, not just another tool.

Stop Repeating ESLint & Prettier Setup in Every Project

Ankesh Sharma — Wed, 11 Mar 2026 16:50:25 +0000

While starting new projects, I noticed I was repeatedly doing the same setup — configuring ESLint and Prettier every single time.

It didn’t make much sense.

Setting up linters and formatters repeatedly across projects is not only time-consuming but also inefficient. Most projects share the same base rules anyway.

So I created a shared configuration package that I can reuse across projects.

With this setup:

You install the package
Extend the configuration
Add project-specific rules on top if needed

And that’s it. The whole setup takes just a couple of minutes instead of repeating the same configuration again and again.

This helps keep:

Code style consistent
Setup time minimal
Configurations centralized and easier to maintain

I’ve open-sourced the configuration so others can use it or suggest improvements.

GitHub Repo:
https://github.com/iamankeshsharma/eslint-config

NPM Package:
@iamankeshsharma/eslint-config

If you check it out, I’d really appreciate feedback on how it can be improved.

Always open to suggestions 🚀

How should we remember syntax?

Ankesh Sharma — Sat, 07 Mar 2026 14:21:08 +0000

I have droped a short text on this here: https://www.linkedin.com/posts/devankesh_i-was-looking-for-an-ide-that-doesnt-provide-share-7436031901963812867-7xwd?utm_source=share&utm_medium=member_desktop&rcm=ACoAADDQ_lwBJuc45M9zvJaz9B0y9y4e2Tjlhik

Developed my first portfolio.

Ankesh Sharma — Sat, 31 Jan 2026 12:53:18 +0000

This is a submission for the New Year, New You Portfolio Challenge Presented by Google AI

About Me

I'm a web developer, Developed this to express my technical proficiency in developing websites.

Portfolio

How I Built It

Used react, python flask.
Used antigravity for most of the base setup and bug resolution.
other things are written by me.

Design for portfolio is complete.

Ankesh Sharma — Wed, 21 Jan 2026 07:02:25 +0000

Just completed design of portfolio little late but yeh now it complete.
Will start implementing.

Starting Collecting Initial Inspiration for Portfolio

Ankesh Sharma — Sat, 03 Jan 2026 06:34:13 +0000

Collecting Inspirations for Portfolio to join New Year, New You Portfolio Challenge