eslint
This skill configures ESLint to lint JavaScript, TypeScript, and React code in .NET repositories that include frontend assets. It detects existing configurations, installs dependencies locally, and establishes repeatable lint commands in your build pipeline. Use it when your repo has package.json, frontend source files, or explicit linting requests.
ESLint for Frontend Assets in .NET Repositories sets up JavaScript and TypeScript linting for .NET projects with Node-based frontend code.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-25
ESLint for Frontend Assets in .NET Repositories sets up JavaScript and TypeScript linting for .NET projects with Node-based frontend code. This skill configures ESLint to lint JavaScript, TypeScript, and React code in .NET repositories that include frontend assets. It detects existing configurations, installs dependencies locally, and establishes repeatable lint commands in your build pipeline. Use it when your repo has package.json, frontend source files, or explicit linting requests.
Use it when
- ESLint supports TypeScript through the @typescript-eslint parser and plugin.
- ESLint React rules configuration requires the eslint-plugin-react package.
Verify before relying
Read SKILL.md below before installing (2 files). Open directory: indexed for reading, not audited.
Install
managedcode/dotnet-skills/eslint · repository language: C#
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I set up ESLint for .NET JavaScript frontend?
ESLint is a static analysis tool that enforces code quality in JavaScript and TypeScript. To set up ESLint for your .NET JavaScript frontend, install it locally via npm or yarn in your frontend directory, create an .eslintrc configuration file specifying your environment (browser, Node.js, or both), and define which rule sets to extend (e.g., eslint:recommended). For .NET repos with package.json, ESLint integrates alongside your existing build tools and can be invoked via npm scripts or CI/CD pipelines.
What is the process to lint TypeScript in ASP.NET Core?
ESLint supports TypeScript through the @typescript-eslint parser and plugin. To lint TypeScript in ASP.NET Core, install @typescript-eslint/eslint-plugin and @typescript-eslint/parser, update your .eslintrc to specify the TypeScript parser, and add typescript-eslint rules to your configuration. Point ESLint at your .ts and .tsx files using glob patterns in your lint command, then integrate the command into your ASP.NET build or CI/CD workflow for automated validation.
How do I configure ESLint React rules?
ESLint React rules configuration requires the eslint-plugin-react package. Install it, then add 'react' to the plugins array in your .eslintrc and enable recommended rules via extends: ['plugin:react/recommended']. Configure React-specific settings like the JSX pragma and version detection. For TypeScript React projects, combine this with @typescript-eslint and eslint-plugin-react-hooks to enforce best practices for hooks and component patterns.
Can ESLint automatically fix JavaScript errors?
Yes, ESLint includes an auto-fix feature. Run eslint --fix on your source files to automatically correct many common issues like formatting, unused variables, and import ordering. Not all rules support auto-fix; some require manual intervention. Use --fix in your development workflow or pre-commit hooks, and integrate it into CI/CD to catch and repair issues before they reach production.
How do I integrate ESLint into my CI/CD pipeline?
ESLint integrates into CI/CD by adding a lint step to your pipeline configuration (GitHub Actions, Azure Pipelines, etc.). Install ESLint and dependencies in your build environment, run eslint with a glob pattern targeting your frontend source files, and fail the build if violations exceed your threshold. Store your .eslintrc in version control so all environments use consistent rules. This ensures frontend code quality is validated on every commit or pull request.
What does ESLint ignore patterns and scoping do?
ESLint ignore patterns prevent linting of specified files and directories. Use an .eslintignore file or the ignorePatterns property in .eslintrc to exclude node_modules, build outputs, and generated files. Scoping rules to specific file types (e.g., .js, .ts, .jsx) via overrides in your config lets you apply different rule sets to different parts of your codebase, such as stricter rules for source files and relaxed rules for test files.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
ESLint for Frontend Assets in .NET Repositories
Trigger On
- the repo has
package.json,eslint.config.*,.eslintrc*,tsconfig.json, or JS/TS/React frontend files - the user asks for JavaScript or TypeScript linting, React rule enforcement, import hygiene, or unsafe frontend patterns
- CI should fail on frontend lint findings instead of relying on editor-only feedback
Do Not Use For
- CSS ownership by itself; route that to
(truncated - see the full file via the links below)
File tree — 2 files
catalog/Tools/ESLint/skills/eslint/SKILL.md
catalog/Tools/ESLint/skills/eslint/manifest.json
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Set up ESLint for JavaScript/TypeScript linting in .NET repos”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Metalint aggregates multiple frontend linters into a single CLI entrypoint for .NET repositories with Node-based assets. It delegates to ESLint, Stylelint, HTMLHint, and similar tools while keeping their configs explicit and reviewable under `.metalint/`. Use it when your repo already has multiple linters and needs orchestration, not when a single tool like Biome covers your needs.
sonarjs integrates SonarJS-derived rules into ESLint for .NET repositories shipping JavaScript or TypeScript frontends. It surfaces cognitive complexity limits, bug-prone patterns, and maintainability issues beyond baseline linting, supporting both local developer workflows via eslint-plugin-sonarjs and server-side SonarQube or SonarCloud gates.
Biome integrates into .NET repositories to provide combined formatting, linting, and import organization across JavaScript, TypeScript, CSS, JSON, GraphQL, and HTML. The skill handles ownership decisions between Biome and existing tools like ESLint or Prettier, generates configuration, and establishes repeatable commands for CI and local development. It guides migration strategies and validates that your build and test flows remain stable after changes.
Chous adds architectural guardrails to growing frontend codebases in .NET projects by linting folder structure, naming conventions, and file placement against a checked-in policy. It runs as a CLI gate to catch layout drift before it compounds, complementing semantic linters without replacing them. Use it when structure policy matters more than syntax enforcement.
htmlhint enforces HTML structure and attribute correctness on static files and built output in .NET repositories. Target rendered HTML in folders like wwwroot/ or dist/ rather than raw server-side templates, keeping validation separate from JavaScript and full-site audits.
Stylelint brings CSS and SCSS linting to .NET projects that bundle stylesheets alongside web frontends. Set up repo-local configuration, define clear ownership boundaries, and enforce naming conventions and duplicate-style cleanup without conflicting with other linters.
More skills webhint (MIT) · ultracite (MIT) · ultracite (MIT) · eslint (MIT) · modern-csharp (MIT)