Hi everyone,
I’ve released Frappe Inspector, a JetBrains plugin built specifically for developers working with Frappe Framework and ERPNext projects.
The idea came from a fairly simple frustration: JetBrains IDEs understand Python, JavaScript and JSON individually, but they do not understand how a Frappe project connects all of them together.
Frappe Inspector adds that missing project-level context.
It can currently help with:
- Detecting Frappe Bench installations and individual Frappe apps
- Browsing apps, modules, DocTypes and fields
- Navigating between DocType JSON files, Python controllers, client scripts and tests
- Completing known DocType and field names
- Detecting unknown DocTypes and likely invalid field references
- Navigating and validating
patches.txt - Performing basic validation of
hooks.py - Comparing schema changes and identifying potentially risky migrations
- Finding references to removed fields
- Exploring DocType relationships and permissions
- Inspecting hooks, fixtures and whitelisted methods
The goal is not to replace Bench, the Frappe documentation or proper testing.
It is simply meant to catch some of the easy-to-miss problems while you are still editing the code, before you discover them during migration or after deployment.
There is a free Community feature set, and the more advanced analysis tools are available in Pro. The same plugin is used for both; the basic features remain available without a Pro license.
JetBrains Marketplace:
Documentation, issue tracker and feature requests:
This is still a young project, so feedback from people working on real Frappe and ERPNext codebases would be especially valuable.
I would genuinely like to hear about:
- Incorrect assumptions about Frappe project structures
- False-positive diagnostics
- Missing DocType patterns
- Performance problems on large benches
- Compatibility issues with specific Frappe or JetBrains versions
- Features that would actually save time in daily development
Criticism is welcome, including blunt criticism, as long as there is enough detail for me to understand and reproduce the problem.
As a small thank-you, the person to report a confirmed critical bug will receive one month of Frappe Inspector Pro for free. The report must include clear reproduction steps and demonstrate a serious impact such as data loss caused by the plugin, a major IDE failure, a security/privacy issue, or a working Pro-license bypass. Cosmetic issues and ordinary false positives do not count as critical bugs.
Please do not include private customer code, credentials, database dumps or license information in public issues.
Thanks to anyone who gives it a try.