We Melted in Silence — But We Shipped in Bulk 🧀🚀

Hi there,

It’s been a while — and for good reason.
Over the last months, we’ve been deep in the trenches: pitching racletteJS to funding- and application partners, talking to tons of developers, showing up at conventions, and laying down the groundwork for long-term stability of the engine. Checkout the awesome presentation which one of our Heads in Cheese - Michelle - gave at the Alasca Summit 2025! She introduced the openstack-billing-dashboard and gave a little hint towards the next official plugin which might `slide` in your pans within the next couple of weeks... 

But while we weren’t sending newsletters… we were shipping. A lot.
So let’s melt right into what’s new.

---

🚧 A More Capable, More Forgiving Backend

The backend got multiple quality-of-life updates that make racletteJS more resilient — and kinder when things go wrong.

Highlights:

• Added restore endpoints for tags, users, compositions and interactionLinks

• Project dataTypes can now store config values

• getAll routes now properly respect filters

• Improved handling of isDeleted items across the board

• Token TTL now correctly uses the value configured raclette.config

This means no more accidental dead-ends and more control over your portal's data lifecycle.

---

🖼️ A More Flexible, More Intuitive UI Layer

We focused heavily on removing friction for users and developers alike.

Frontend additions & improvements:

• Usermenu can now render compositions inline when no interactionLink trigger is provided

• Appbar:

  • supports interactionLinks & inline compositions

  • can now launch compositions in floating windows (this is a work in progress though)

• Token expiry now auto-redirects to login and returns users to where they left off

• Search fields now support custom labels + debounce

• PageNavigation can now be configured to show interaction link titles on mouseover

• Inline compositions now possible for interactionLinks 

• Tailwind now uses class-based dark mode sync

• Composition slots now receive routeParams as props this gives you more possibilities to manipulate your widget states via the raclette routing!

• Numerous cache, layout, i18n, and welcome-screen fixes

This all adds up to smoother transitions, fewer flickers, more predictable layout behavior — and a UI layer that listens more closely to your intentions.

---

🧰 Workbench: More Control, Better Management

The Workbench keeps maturing into a proper power tool.

New capabilities:

• Restore deleted items directly from the UI

• Hard delete support for all core types

• Appbar triggers for interactionLinks

• Prepend/append actions for table rows in the BaseDataTable component

• Project configuration interface, where you will find more and more config params in the future to configure your portal more granularly

• New fields & options for composition and dynamic forms (slotLayout, objectList, datePicker)

• UI polish & bug fixes across welcome screen, i18n, tags, plugin logic

The Workbench is quickly becoming the place where complex racletteJS setups can be managed without fear and without Developing knowledge.

---

🔧 Quality Fixes & Stabilization

Across versions (0.1.12 – 0.1.18), we resolved dozens of long-standing issues:

• Deleted composition handling

• Axios delete issue

• Race conditions in parent/child query cache

• Widget rerenders

• Missing i18n keys

• InteractionLink translations

• Tailwind & theme sync

• Vite alias fixes (@app)

• Welcome screen layout issues

• Filters not respected in core backends

• Legacy subscriber logic removed

The short version:
racletteJS is smoother, more predictable, and less surprising.

---

📦 Releases

The past months bring us to:

• @raclettejs/core: up to v0.1.18

• @raclettejs/workbench: up to v0.1.18

• @raclettejs/types: up to v0.1.18

More stability, more capability — fewer hiccups.

---

🎉 What’s Next

We’re almost ready to share more about the long-term roadmap we’ve been quietly preparing behind the scenes:
funding, partnerships, platform sustainability, first big adopters and the next big milestones for raclettejs.
As from the next year, we aim to have everything in place to make the whole strategic planning process out in the open and make sure everybody can participate! 
We are also close to moving all our components into a modern yarn4 monorepo. As from then we will be able to reimplement our testing strategies and publish our first fullstack racletteJS plugins which are only waiting for the new release processes. 

But first we wanted to get this big batch of changes into your hands.
Thanks for building, testing, and dreaming with us — even when it gets a bit quiet between melts.

Until next melt,
Sincerely yours, The Cheesy People