pf-import-checker

To fix unresolved PatternFly chart imports, audit your codebase to ensure chart imports are sourced from the correct subpath within @patternfly/react-charts. This enforces compatibility with Victory-based and dynamic loading mechanisms.

Broken PatternFly chatbot module resolution happens when import paths are misconfigured. You must enforce chatbot imports strictly from @patternfly/chatbot/dist/dynamic/* to support proper runtime loading and resolve the modules correctly.

The correct import path for PatternFly component groups is @patternfly/react-component-groups/dist/dynamic/*. Enforcing this specific dynamic subpath ensures proper module resolution and supports dynamic rendering across your application.

You can audit your codebase for missing PatternFly CSS imports by running a static analysis check on your project. This process validates import paths and flags any missing CSS dependencies that could break component styling.

Yes, the PatternFly import checker works with both JavaScript and TypeScript codebases. It validates and corrects import paths across both environments to ensure correct module resolution for charts, chatbot, and component groups.

The best way to prevent misconfigured PatternFly dynamic import paths is to run a static analysis audit that enforces correct subpaths for charts, chatbot, and component-groups. This provides actionable fixes for common module resolution errors.