š§ racletteJS Fresh Melt ā Core 0.1.21, Widgets Ready & Plugins Cooking
Get the latest updates, insights, and exclusive content from raclette delivered directly to your inbox. Join our community of developers!
š§ racletteJS Fresh Melt ā Core 0.1.21, Widgets Ready & Plugins Cooking
Hello fellow racletteers!
This week brings a fresh release across the core packages and a few important ecosystem updates.
A lot of the work focused onĀ performance improvements, developer experience, and foundational featuresĀ that will support upcoming capabilities like the modular permission system and the typesafe router.
Letās take a look at what melted into the codebase.
š New Release: racletteJS 0.1.21
This week we releasedĀ version 0.1.21Ā for all core packages.
@raclettejs/core
š§ Smarter Route Param Handling
A small but important improvement:
Route parameters that clearly representĀ booleans or numbersĀ are now automatically parsed before reaching widget props. Thanks Javascript
Example:
/dashboard?compact=true&page=2
Previously everything arrived as strings.
NowĀ trueĀ becomes a boolean andĀ 2Ā becomes a number.
This is currently anĀ intermediate solutionĀ until the upcomingĀ typesafe routerĀ lands.
ā” Performance Improvements
SeveralĀ global performance optimizationsĀ landed this release.
Nothing flashy here ā just the kind of quiet engineering work that makes racletteJS applications run smoother and scale better.
š Backend Permission Infrastructure
Backend routes of theĀ corePluginĀ now use a new middleware:
checkPermission
This prepares the backend for the upcomingĀ modular permission system, which will allow much more granular access control across racletteJS applications.
š§© New Widget Lifecycle Hook
All widget components now receive a new prop:
onAllWidgetsReady
This function is triggeredĀ once all widgets within the current composition have rendered content to the DOM.
This enables new patterns such as:
- coordinated widget initialization
- layout synchronization
- performance measurement
- inter-widget orchestration
š Work Sessions (Sharing with Non-Authenticated Users)
A new global concept has been introduced:
Work Sessions
These allow you toĀ share a document with users who are not authenticated.
This opens up use cases such as:
- temporary collaboration links
- external stakeholder access
- preview environments
- simplified onboarding flows
Expect this feature to evolve further as collaboration features grow.
š” Backend Rate Limiting
racletteJS now supportsĀ rate limitingĀ out of the box.
Configuration is available via:
raclette.config ā backend config
Under the hood this uses:
@fastify/rate-limit
This adds an importantĀ security and abuse protection layerĀ for racletteJS backend APIs.
@raclettejs/workbench
Workbench also received updates inĀ 0.1.21.
š Configurable Widget IDs
You can now configure theĀ widgetIdĀ directly in the composition layout screen.
This improves:
- debugging
- referencing widgets
- layout control in complex compositions
š Improved Widget Browser
TheĀ WidgetList.vueĀ component (used in the widget layout editor) received a new design.
New capabilities include:
- widget search
- widget filtering
- improved visual structure
This makes large widget libraries much easier to navigate.
š raclettePlugins Update
Development has started on a new plugin:
racletteJS Nodemailer Plugin
The plugin will provideĀ email delivery capabilities for racletteJS applicationsĀ using Nodemailer. We will also provide a way for you to design you mailtemplates within the plugin config in the workbench.
Typical use cases will include:
- notification emails
- user onboarding flows
- system alerts
- transactional messages
Itās still early, but the groundwork has begun.
š Ecosystem Updates
š³ Infrastructure Update ā Dependency Containers Upgraded
Weāve upgraded theĀ core dependency containers across the racletteJS ecosystemĀ to their latest stable versions.
This includes updates for services such as:
- Valkey
- MongoDB
These upgrades bringĀ performance improvements, better long-term support, and compatibility with future racletteJS features.
š¦ MongoDB Upgrade Considerations
If you are running racletteJS applications in production ā such as theĀ OpenStack Billing DashboardĀ ā we recommend following theĀ MongoDB migration guide before upgrading.
The migration isĀ a bit tedious, because MongoDB requires stepping throughĀ multiple intermediate upgrade versions. The guide walks you through the process.
What Happens If You Skip the Migration?
If you chooseĀ not to follow the migration path, be aware that you will loose all data stored in the database, such as:
- users
- API configuration
- compositions
- interaction links
- custom datatypes
Can I Stay on MongoDB 5?
Yes.
There areĀ no known security risksĀ in staying on MongoDB 5 for now, so upgrading isĀ not mandatory.
However,Ā MongoDB 8 provides a significant performance boost, which we strongly recommend taking advantage of once possible.
š Monorepo Status
Good news for all core Contributors!:
TheĀ racletteJS monorepo setup finally behaves the way we want it to.
While the developer experience is still being refined, the core architecture is now working reliably.
One area we're currently improving isĀ simultaneous development of applications, plugins, and the core framework.
If you want to do this already, check out the guide:
Expect further improvements here ā good tooling is essential for a healthy open-source ecosystem.
š„ What This Means
This weekās release focuses heavily onĀ foundation work:
- performance improvements
- widget lifecycle capabilities
- security via rate limiting
- early collaboration features
- ecosystem plugin growth
These kinds of releases might look small at first glance, but they quietly unlockĀ a lot of future capabilities for racletteJS applications and platform deployments.
And as always ā more cheesy things are cooking behind the scenes.
Until the next melt š§
The Cheesy People
Newsletter from March 6, 2026