Task

Refactor Analyzer addresses a practical task: A static analysis tool for refactoring hints through AST. TypeScript Node CLI and reports.

This is a personal learning project (completed and in use), where specific patterns and tools were practiced without unnecessary overhead.

The case demonstrates an approach to tasks in the area of "Full-stack web applications and dashboards": from setting up to delivery with a clear module structure.

Before starting, we established readiness criteria: a clear first screen, predictable form errors, and the ability to enhance without rewriting half of the codebase.

Solution

A learning but fully functional implementation was made with an emphasis on code readability and reproducible builds.

The scenarios were designed so that the main actions fit within one or two screens: fewer switches, fewer input errors. Navigation and field labels were aligned with familiar patterns—users do not need to "learn the interface".

Special attention was given to loading states and empty lists: skeleton/spinner where data comes asynchronously, and clear empty-state texts instead of an empty table.

Architecture and stack

Server and data: Node.js.

Infrastructure and utilities: TypeScript, AST.

Language distribution in the repository: TypeScript (97.9%), JavaScript (2.1%).

Layers are separated so that the UI does not know transport details: API/storage adapters, domain types, presentation components. This simplifies backend replacement and targeted UX tweaks.

Key features

• TypeScript — used in product logic: reduces the amount of custom code and speeds up the addition of new screens.
• Node.js — used in product logic: reduces the amount of custom code and speeds up the addition of new screens.
• AST — used in product logic: reduces the amount of custom code and speeds up the addition of new screens.

Additionally:

• Integration and use of TypeScript in product logic and interface.
• Integration and use of Node.js in product logic and interface.
• Integration and use of AST in product logic and interface.

Result

The project has been brought to a working state: the team/user receives a stable tool instead of manual tables and correspondence. Time for routine operations has been reduced due to automation in the interface.

The source code is open: https://github.com/astropsy999/refactor-analyzer — you can evaluate the module structure and commit style.

What I would improve

The next step is observability (logs/metrics), regression tests, and API documentation for integrators. For high-load scenarios—profiling bottlenecks and caching reference data.