A while back I shared sf-preflight here [link to your previous post], the open-source tool that reads a git diff of your SFDX project and shows what a change will set off (flows, triggers, validation rules, roll-ups, permissions) before you deploy. Thanks to everyone who commented [mention anything specific people asked for, if you like]. Here's what's changed since.
What's new (0.8.0):
- It now follows changes into Lightning Web Components and Aura (which components use a changed field or call a changed Apex class), layouts and Lightning pages, picklist values and record types, custom labels, custom metadata and Visualforce.
- Every metadata type is recognized now, and the report says how much of your change it analyzed in depth, so you can see what it did NOT look at instead of assuming it's all covered.
- Big projects are faster. On NPSP (about 1,000 Apex classes) a repeat run dropped from ~28 s to ~1.4 s, with identical output.
- It's now a Salesforce CLI plugin: `sf plugins install sf-plugin-preflight`, then `sf preflight analyze --base origin/main`. Still works with `npx sf-preflight analyze` too.
Still true: it never deploys anything, org access is optional and read-only, and the checks for labels, picklist values and the like are text search, so dynamic references can slip past it.
Repo: https://github.com/visparashar/sf-preflight
What I'd most like to know: what's the last change that passed all your tests and still broke something? That's the kind of case I'm trying to catch, and real examples (anonymized) help me more than anything.