Hi Luca,
I don't think Mendix has published many end-to-end examples specifically for the "Web Extensions consistency checks in MxBuild" feature yet.
What changed in Mendix 11.9 is that MxBuild can execute validation logic from Web Extensions during the build process instead of only inside Studio Pro. This allows custom widgets/extensions to raise consistency errors that can fail CI/CD builds, making automated validation possible.
In practice, the pattern is roughly:
Plain Text
Studio Pro
↓
Web Extension
↓
Consistency Check API
↓
MxBuild
↓
Build Warning / Error
Some things I'd look at:
The Web Extension examples in the Mendix SDK documentation.
Existing Mendix Marketplace widgets that already expose custom consistency checks.
The generated TypeScript code for Web Extensions created with newer versions of the tooling.
The Mendix Release Notes around Studio Pro 11.9+ where MxBuild support for Web Extension validations was introduced.
A simple use case could be checking:
Plain Text
MyWidget:
- Property A required when Property B is enabled
- Raise Warning if missing
- Raise Error if configuration is invalid
Then:
Plain Text
Local consistency check
and
MxBuild CI pipeline
would report the same issue.
One thing to be aware of is that because Deno is now involved in executing extension logic, build agents running MxBuild may need to allow the Deno execution environment and associated tooling. If you're experimenting in CI/CD, I'd test there early as well.
From what I've seen, the functionality is still relatively new, so you may find more examples by inspecting newer Mendix widget projects rather than finding dedicated documentation. If your goal is to create a custom consistency check, I can provide a minimal Web Extension example that raises warnings/errors during MxBuild.