Marionette 5.2.0: Meet Skeletor.
Marionette 5.2.0 adds support for Skeletor’s Models and Collections and introduces a DOM API for trusted raw markup.

Backbone stopped being a core dependency in Marionette 5.0. It didn’t stop being useful. In 5.2, there’s another option for people who like Backbone’s Models and Collections: Skeletor. Apparently we do have a policy about skeletons.
Who might want Skeletor?
Skeletor is a TypeScript-first data library that powers Converse.js, an open-source XMPP chat client. It takes the familiar Model and Collection ideas from Backbone and adds typed attributes, computed properties, and persistence options such as IndexedDB and REST. It leaves Views and routing to the application.
It’s worth a look if you’re starting a TypeScript app and want model objects that know when their data changes, or if you’re trying a new data layer in one feature of an existing Backbone app. For example, a contact model can store a first and last name and give the View a computed display name without adding that extra field to what gets saved.
The optional @mnjs/adapters/skeletor adapter connects Marionette Views and CollectionViews to Skeletor 4.0.3. Templates can read computed values alongside stored attributes, and ordinary collection changes keep the child Views for models that are still present. If you’re bringing a Backbone app to Marionette 5, you can keep your existing Models and Collections through the Backbone adapter and try Skeletor in a new feature.
One small DOM API
DomApi.setUnsafeHtml(el, markup) gives integrations an explicit way to put trusted raw markup, such as an SVG icon string, into a container they own. It doesn’t sanitize the string or clean up Views. Keep using your renderer for the content it owns.
Marionette, Utils, Radio, Data, and Adapters move to 5.2.0 together. HTML, Router, and the test helpers keep their own versions.
Read the 5.2.0 release notes or see the Skeletor adapter example.