Hello fellow racletteers!

This update is a bit less experimental chaos and a bit more “making the platform actually pleasant to build with every day”.

A lot happened across the racletteJS ecosystem over the last releases:

new exporter foundations including an amazin reusable DataTable component, improved Docker generation, Workbench polishing, and a surprisingly huge leap for the OpenStack Billing Dashboard.

In other words:

The ecosystem is becoming increasingly production-shaped.

Let’s see what melted into the stack 🧀

---

🚀 New Releases: racletteJS 0.1.25 → 0.1.35

This release cycle focused heavily on:

• improving deployment reliability
• stabilizing build tooling
• preparing reusable data handling systems
• reducing friction in plugin and platform development
• strengthening the foundation for future ecosystem apps

And yes: some features already started showing up in real-world racletteJS applications.

---

@raclettejs/core

📦 Core Exporter / Importer Foundations

One of the biggest additions in this cycle:

racletteJS now ships the foundation for a universal exporter/importer system.

Included now:

• core exporter/importer functionality
• a new core baseDataTable foundation

This is an important building block for future ecosystem-wide data portability and reporting features.

The long-term goal is to make serializers and exports reusable across apps and plugins — instead of every project reinventing exports differently. Take that, vendor lockin!

You can already see the first real-world usage of this in the OpenStack Billing Dashboard update further below 👀

---

🐳 Better Build & Deployment Experience

A lot of work went into improving generated infrastructure and deployment defaults.

Build improvements include:

• improved build-helper handling
• improved generated docker-compose files
• added missing healthchecks to generated examples
• increased default build timeout to 240s
• fixed missing publish folders
• fixed wrong default environment variables in generated compose setups

This especially improves reliability for:

• CI pipelines
• slower machines
• larger Docker-based deployments
• first-time setup experiences

Currently the build process is under big maintenance though. So stay tuned for this!

---

🧩 Frontend & Plugin Improvements

Several frontend and plugin development issues were cleaned up:

• hardened Vue script detection in the Vite plugin
• restored missing service type exports
• fixed TypeScript export issues
• improved dependency optimization handling
• latest autogenerated shared core files included again

Small change. Large reduction in daily annoyance.

---

🔒 Stability & Backend Fixes

A number of backend edge cases and operational quirks were resolved:

• fixed hard delete behavior for users
• sanitized default rateLimit handling
• removed outdated custom notFound handling
• fixed unwanted DEBUG_MODE activation

---

@raclettejs/workbench

Workbench mostly focused on refinement this cycle.

Improvements include:

• restyled dynamicForm components
• fixed non-removable interactionLink triggers
• dark theme fixes and missing color handling
• dependency updates and alignment with latest core releases

Not flashy. Still pretty.

---

🌍 Ecosystem Updates

☁️ Major Upgrade: OpenStack Billing Dashboard

The OpenStack Billing Dashboard — built entirely with racletteJS — received a massive upgrade.

And honestly: this release is a pretty good showcase of where the ecosystem is heading and how racletteJS can help with building platforms.

New Features

💰 Flavor Pricing Directly From OpenStack:

Flavor information is now loaded directly from Nova. No more manually guessing flavor names.

📄 Export & Reporting Features:

The new export foundations inside racletteJS are already being used in production.

The Billing Dashboard now supports:

• server list export
• XRechnung export
• ZUGFeRD export

This is an important milestone because it validates the idea of reusable export infrastructure across racletteJS applications.

💱 Better Pricing UX:

Pricing can now be entered either in cents or directly in the main currency unit.

➡️ All of these feature had been proposed feature requests within the projects Gitlab. Thanks to everyone who helps improving the dashboard with their ideas!

🔥 What This Means

This release cycle was about platform maturity.

Not in the “big marketing launch” sense.

But in the:

• deployments becoming more reliable
• exports becoming standardized
• applications becoming interoperable
• tooling becoming less fragile
• ecosystem apps becoming production-capable

sense.

The pieces are slowly connecting together now.

And many of the things that previously existed as isolated features are starting to become shared platform capabilities.

In other words:

👉 racletteJS is increasingly behaving like an actual ecosystem — not just a framework.

Until the next melt 🧀

The Cheesy People