
Experience Builder includes an in-browser code editor for creating JavaScript components. The UI handles Preact/React compilation with Tailwind CSS support, allows prop and slot configuration, delivers real-time previews, and stores components as config entities.
We're aiming to develop a new CLI tool to establish an alternative workflow, empowering developers to build components in their preferred environment and seamlessly integrate them with Experience Builder.
Initial goals
- CLI-specific authentication
- Downloading components
- Uploading components
- Scaffolding components
- Building compiled code:
- Compiling JavaScript code written as Preact components
- Transpiling CSS code
- Building CSS with Tailwind CSS
POC
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | xb-cli-issues.png | 312.21 KB | balintbrews |
Comments
Comment #3
balintbrewsComment #4
balintbrewsComment #5
wim leersJust discovered over at #3502640: Camelcase the client-side representation of code components that:
CLI vitestCI job to failIt's that second bit that worries me — I think that's missing from this meta (and IMHO should've been done for every incremental CLI command added).
Comment #6
balintbrewsOur timeline to deliver the initial version of the CLI didn't allow for setting up the required automation and CI for integration tests. I hope we can prioritize that soon. Until then, what will definitely improve the situation is that we're planning to start sharing code between
uiandclionce we get to #3525592: CLI command to build Tailwind CSS for code components, which will mean shared TypeScript type definitions for how the component payloads should look like. That will catch a lot of problems already by static analysis.Comment #9
balintbrewsComment #12
balintbrews