Hello fellow racletteers!

This week’s update is a bit more hands-on and infrastructure-heavy — with improvements that you will definitely notice if you’ve been working with the file system, plugin hotreload, or the workbench.

Also: yes… racletteJS now runs natively on Windows. We have questions too.

Let’s see what melted into the stack.

---

🚀 New Release: racletteJS 0.1.24 → 0.1.25

We’re shipping two closely packed releases, bringing improvements across core, workbench, and the plugin ecosystem.

The focus this time:

• fixing long-standing quirks
• improving developer experience
• preparing the ground for upcoming features

---

@raclettejs/core

🧩 Virtual File System Overhaul

The virtual file system (VFS) received a major internal rework.

• now based on globbing + hardlinks
• eliminates many previous issues with:
  • missing mounts
  • symlink inconsistencies

This should make local development setups significantly more predictable.

👉 One important caveat:
Hardlinks do not work across partitions, so make sure your app and core live on the same partition.

---

🪟 Native Windows Support

Yes, really.

racletteJS can now run natively on Windows without requiring a Unix shell.

We’re not saying you should.
We’re just saying you can.

---

🔧 Build & Tooling Fixes

A number of issues that affected day-to-day development are now resolved:

• ESLint is fully working again with proper Vue + TypeScript parsing
• build process fixed when no workbench override is present
• improved config generation for frontend paths
• clearer error messages for duplicate plugin registrations

Additionally:

• ESLint stack aligned to v9-compatible versions
• Tailwind ESLint plugin temporarily removed
• Vite dependency optimization temporarily disabled (pending fix)

---

🔌 Plugin & DX Improvements

• local plugin registration now supports directory fallbacks (src/frontend, src/backend)
• new @app alias for backend (parity with frontend)
• widget metadata handling improved:
  • optional icon, color, images
  • deterministic fallbacks (generated color, placeholders)

This makes rapid prototyping of plugins and widgets much smoother.

---

👤 Temporary Self-Service API

A new endpoint has been introduced:

• patchOwn → allows users to edit their own user object

This is a temporary bridge solution until the full permission system lands — but already unlocks important self-service capabilities.

---

@raclettejs/workbench

✨ Composition UX Improvements

Workbench continues to get incremental but meaningful UX upgrades.

• auto-generated pathnames for compositions based on title
  • simple slug strategy (lowercase, dashes, clean URLs)
  • stops syncing once manually overridden
• improved widget fallback rendering:
  • missing metadata now shows deterministic placeholders
  • enables fast prototyping without assets

---

🧠 Better Editor Feedback

• widget selection sidebar now shows tooltips with full titles
  → small change, big usability win in larger setups

---

🧩 CRM & Project Management Evolution

We are currently working on a new project management tool, which will also include a new CRM plugin.

This means:

• the current cheesy-crm app will not be worked on anymore we will instead
• replace it with a CRM plugin

This will make sure that the CRM dataTypes can be combined freely with any other racletteJS plugin or app

---

🌍 Ecosystem Updates

🗂️ VFS Stability (Almost There)

The new VFS removes many previous issues — but one known problem remains:

• permission mismatches caused by Docker user vs host user

In short:

files written as root in the container are not always friendly on the host

We’re actively working on a proper resolution here.

---

🎨 Vuetify 4 Everywhere

All plugins can now leverage Vuetify 4 features consistently.

What’s coming next:

• updated baseDataTable built on the new API
• a universal export system for data tables

Planned export formats:

• JSON
• XML
• YML
• CSV

And yes — also:

• xRechnung export (starting with the billing dashboard)

This will also serve as a reference implementation for writing serializers inside racletteJS.

---

🔥 What This Means

This release is less about flashy features and more about removing friction.

• the VFS is finally becoming reliable
• plugin development is getting smoother
• workbench UX keeps improving
• the ecosystem is shifting toward composability

And under the hood, foundations are being laid for:

• a proper permission system

• more powerful data handling

• better cross-platform support

• a new database backend

In other words:

👉 things are stabilizing — and expanding at the same time.

---

Until the next melt 🧀

The Cheesy People