Introducing Fluxscape CLI Inspect Commands

Better Visibility, Better Habits, Better Projects

As Fluxscape projects grow, understanding what is actually happening inside an app becomes just as important as building new features. Today we are introducing a new set of CLI inspect commands that focus on exactly that: visibility, quality, and long term maintainability.

These new commands are part of our ongoing effort to give developers better insight into their projects without slowing them down or forcing them into heavy tooling.

With the latest Fluxscape CLI update, you can now inspect components, project TODOs, page structure, and automatically generate a sitemap directly from the command line.

Understanding what lives in your project

The inspect component command gives you a structured overview of all components in a project. It analyzes graph structure, node counts, connections, and applies a growing set of annotation rules.

These annotations highlight things like accessibility issues, potential memory leaks, unused buttons, missing image sources, and visual nodes that are no longer connected to the render tree. Some of these rules are intentionally strict. They are designed to encourage better building habits and catch issues early, before they turn into technical debt.

The output is returned as structured JSON, making it easy to consume programmatically, integrate into CI workflows, or simply scan manually when auditing a project.

We currently support seven annotation rules, and this list will continue to grow as we see more real-world patterns. In a future version of Fluxscape, these inspections will be powered by real-time project data, enabling even deeper insights while you build.

Making TODOs visible again

TODOs have a habit of disappearing into graphs over time. The inspect todo command solves this by collecting all TODOs across the project into a single, clean output.

The CLI scans function and script nodes for JavaScript TODO comments, as well as graph comments marked with TODO. The result is a clear overview of unfinished work, grouped by component and location.

This makes it much easier to review technical debt, prepare refactors, or simply understand what still needs attention before a release.

Seeing your app structure clearly

The inspect page command lists all pages in a project and their hierarchy. This is useful for onboarding, audits, and sanity checks as applications evolve.

Building on the same data, the inspect sitemap command generates a sitemap.xml file that can be used for SEO. For applications that use dynamic routes, placeholders such as app/product/{id} are included. Support for fully resolved dynamic paths will continue to improve as the tooling matures.

A step toward smarter tooling

These new inspect commands are an important step toward deeper static analysis and better project hygiene in Fluxscape. They are not meant to replace good judgment or experience, but to support it with clear signals and actionable insights.

As always, feedback from real projects is what shapes Fluxscape the most. Try the new inspect commands, integrate them into your workflow, and tell us what you would like to inspect next.

This is just the beginning.

Want to test it out on your own project? Contact us at https://www.fluxscape.io/contact