troubleshoot

Diagnose and resolve ESO Log Aggregator development environment issues via commands.

2|Updated Aug 18, 2025

Search Tags:#typescript #debugging #troubleshooting #graphql #development environment #build errors #ci

Ready to run

npx skills add https://github.com/ESO-Toolkit/eso-toolkit --skill troubleshoot-eso-toolkit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: troubleshoot
Source: https://github.com/ESO-Toolkit/eso-toolkit/tree/main/.github/skills/troubleshoot
Command: npx skills add https://github.com/ESO-Toolkit/eso-toolkit --skill troubleshoot-eso-toolkit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides quick-reference fixes for common development environment issues encountered in the ESO Log Aggregator project, helping developers resolve problems efficiently and resume coding.

Core Features & Use Cases

Issue Diagnosis: Quickly identify the cause of common errors like module not found, port conflicts, or build failures.
Automated Fixes: Provides specific commands to resolve issues such as regenerating GraphQL types, fixing linting errors, or reinstalling dependencies.
Use Case: A developer encounters a "module not found" error after cloning the repository. They can use this Skill to quickly find the solution: delete node_modules/ and run npm ci.

Quick Start

Use the troubleshoot skill to fix GraphQL type errors by running npm run codegen.

Frequently Asked Questions about troubleshoot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix module not found errors after cloning a development environment?▼

To fix module not found errors, remove the node_modules directory and run npm ci to reinstall dependencies. This resolves stale or missing packages that cause build failures in the development environment.

Why does my GraphQL code show stale type errors during TypeScript development?▼

GraphQL type errors occur when generated types become stale. Run npm run codegen to regenerate GraphQL types and resolve the TypeScript errors. This synchronizes your schema definitions with the codebase.

What is the best way to resolve port conflicts in a local development environment?▼

Resolving port conflicts requires identifying the occupied port and terminating the process. This troubleshooter provides command-line instructions to diagnose and clear port conflicts, allowing the build process to resume.

How do I fix Playwright browser installation issues during continuous integration?▼

Fix Playwright browser installation issues by executing the specific installation scripts provided. This troubleshooter offers deterministic commands to properly install browsers and resolve CI pipeline failures.

Can I use automated scripts to fix linting and TypeScript build errors?▼

Yes, you can use automated scripts to fix linting and TypeScript build errors. The troubleshooter provides specific commands to automatically resolve linting issues and regenerate types, restoring the build environment.