build(deps): bump the marionette group with 2 updates
Bumps the marionette group with 2 updates: @mnjs/adapters and marionette.
Updates @mnjs/adapters from 5.0.0 to 5.1.1
Release notes
Sourced from @mnjs/adapters's releases.
v5.1.1
We had barely finished saying “5.1.0” when Vite gave us a reason to say “5.1.1.” The runtime stayed put; the example tooling did not.
- Update Vite to 8.3.7 in the shipped Records example and locked tooling fixtures. Vite is example/build tooling, not a Marionette runtime dependency.
- Make Node 26 consumer verification required alongside Node 22 and 24, including installed documentation and exact release-candidate checks.
- Let introductory docs follow the installed package, keeping exact versions for reproducible examples and compatibility requirements. Refresh Router guidance with the recorded Chromium, Firefox and Playwright WebKit coverage.
Marionette runtime implementation and public APIs are unchanged from 5.1.0. The five coordinated packages (
marionette,@mnjs/utils,@mnjs/radio,@mnjs/dataand@mnjs/adapters) are 5.1.1. Router, HTML and test helpers remain independently versioned; this release does not include Router 0.2.0.Install core:
npm install marionette@5.1.1. Keep Utils and Radio aligned with core. Optional Data/Adapters use their declared peer ranges; HTML, Router and test helpers are independently versioned.Changes · Migration guide · Quick start
Immutable release artifact for 8e4b36dbb9b926a733cd4f2aebd68ed19fb15288.
@mnjs/utilstarball SHA-512: 009921feb011ab18c4861c65e422999d72cec7ce2696052bb6b413bb6eccde2649172fbd0335783297e4baafd7213358e45738bcb50cdb50690c12ff5a554ecd@mnjs/radiotarball SHA-512: 5c52ffba295a45fa148e4a8b332939d795bc6b2ec10c5ea60ea2bb9283b8f8e4b93b448000dc6331ddb016ff311d1f3b3f8dfcb302cb0d8586505954ce33903c marionette tarball SHA-512: a67a2adcd43221711e51a1f4540c8ec49e8460fb068562f8ae7855536b11a8af721e4e008f14570f2570448ad9cd8ab393853c167dfc0aa1b8259848f4d6b52f@mnjs/datatarball SHA-512: 98b6ad4dda52798a2ac1985b2ff333fafd71d564b3ce1aa693d7015db752469c1bfa683020d1de70bf4a5d80c34dfb9dfa11de7bff7de9eb0b58c83ea93a509b@mnjs/adapterstarball SHA-512: d475e3ed3bc013309490e08cb9c1e7cc3ed24af3fef3092b8ffb2469eff1d4ffe8c2acc84fb07cfc217357d7d34c404d9ebfc9683d337767c9f5882f0c4e26bcv5.1.0
Apparently, “optional” and “worth a minor release” are not opposites. Marionette 5.1 gives HTML templates and feature-owned routing a proper place in the stack. Two more opinions. Neither compulsory.
Marionette 5.1 brings two independently versioned companion packages into the recommended path for building new applications:
@mnjs/htmlprovides tagged-template rendering, incremental DOM updates, keyed lists, and directives, with a DOM API designed for Marionette-owned Views. Keep interactions inevents,triggers, andui; let the template describe the content.@mnjs/routerconnects named URLs with feature-owned routes and Application lifecycles. Features register their own routes, prepare their data, and manage their child Applications without moving every destination into one central routing file.- Updated guides and agent skills connect the first rendered View to composed and routed features, with executable examples and guidance for testing readiness, interactions, and teardown.
The coordinated packages
marionette,@mnjs/utils,@mnjs/radio,@mnjs/data, and@mnjs/adaptersmove to 5.1.0. HTML, Router, and the test helpers retain their independent versioning. The pre-v1 Router 0.1.1 updates its Catalog example to HTML and its Desk instructions to accept a compatible Adapters version instead of pinning 5.0.1. Its runtime and public API are unchanged; it is published separately from the five coordinated packages. Neither HTML nor Router becomes a required core dependency. Adapters’ core peer and Data’s nonoptional Utils peer now accept^5.0.1; core, Utils, and Radio keep their exact shared-runtime alignment. Data uses the shared Utils instance rather than installing a private copy.Existing compatible renderers, data integrations, and host routers remain
... (truncated)
Changelog
Sourced from @mnjs/adapters's changelog.
v5.1.1
We had barely finished saying “5.1.0” when Vite gave us a reason to say “5.1.1.” The runtime stayed put; the example tooling did not.
- Update Vite to 8.3.7 in the shipped Records example and locked tooling fixtures. Setup instructions select the current Vite 8 release and explain committing the resulting lockfile for reproducible installs. Vite is example/build tooling, not a Marionette runtime dependency.
- Refresh Router guidance for published
@mnjs/router0.1.1 and its passing Chromium, Firefox and Playwright WebKit coverage. Link the tested source archive and document native WebKit fragment/Back differences without changing routing behavior. The runnable companion example now checks Router 0.1.1 with published Marionette 5.1.0 and HTML 1.0.0.- Add Node 26 to required consumer LTS verification alongside Node 22 and 24. Check installed documentation recipes at each line's floor and latest patch; require Node 26 fixtures and recipes against the exact release candidate.
- Move the five coordinated packages
marionette,@mnjs/utils,@mnjs/radio,@mnjs/dataand@mnjs/adaptersto 5.1.1, with matching core/Radio/Utils dependencies. Data's nonoptional Utils peer and Adapters' core peer remain^5.0.1. HTML, Router and the test helpers keep their independent versions.Marionette runtime implementation and public APIs are unchanged from 5.1.0.
v5.1.0
Apparently, “optional” and “worth a minor release” are not opposites. Marionette 5.1 gives HTML templates and feature-owned routing a proper place in the stack. Two more opinions. Neither compulsory.
Marionette 5.1 brings two independently versioned companion packages into the recommended path for building new applications:
@mnjs/htmlprovides tagged-template rendering, incremental DOM updates, keyed lists, and directives, with a DOM API designed for Marionette-owned Views. Keep interactions inevents,triggers, andui; let the template describe the content.@mnjs/routerconnects named URLs with feature-owned routes and Application lifecycles. Features register their own routes, prepare their data, and manage their child Applications without moving every destination into one central routing file.- Updated guides and agent skills connect the first rendered View to composed and routed features, with executable examples and guidance for testing readiness, interactions, and teardown.
The coordinated packages
marionette,@mnjs/utils,@mnjs/radio,@mnjs/data, and@mnjs/adaptersmove to 5.1.0. HTML, Router, and the test helpers retain their independent versioning. The pre-v1 Router 0.1.1 updates its Catalog example to HTML and its Desk instructions to accept a compatible Adapters version instead of pinning 5.0.1. Its runtime and public API are unchanged; it is published separately from the five coordinated packages. Neither HTML nor Router becomes a required core dependency. Adapters’ core peer and Data’s nonoptional Utils peer now accept^5.0.1; core, Utils, and Radio keep their exact shared-runtime alignment. Data
... (truncated)
Commits
Updates marionette from 5.0.0 to 5.1.1
Release notes
Sourced from marionette's releases.
v5.1.1
We had barely finished saying “5.1.0” when Vite gave us a reason to say “5.1.1.” The runtime stayed put; the example tooling did not.
- Update Vite to 8.3.7 in the shipped Records example and locked tooling fixtures. Vite is example/build tooling, not a Marionette runtime dependency.
- Make Node 26 consumer verification required alongside Node 22 and 24, including installed documentation and exact release-candidate checks.
- Let introductory docs follow the installed package, keeping exact versions for reproducible examples and compatibility requirements. Refresh Router guidance with the recorded Chromium, Firefox and Playwright WebKit coverage.
Marionette runtime implementation and public APIs are unchanged from 5.1.0. The five coordinated packages (
marionette,@mnjs/utils,@mnjs/radio,@mnjs/dataand@mnjs/adapters) are 5.1.1. Router, HTML and test helpers remain independently versioned; this release does not include Router 0.2.0.Install core:
npm install marionette@5.1.1. Keep Utils and Radio aligned with core. Optional Data/Adapters use their declared peer ranges; HTML, Router and test helpers are independently versioned.Changes · Migration guide · Quick start
Immutable release artifact for 8e4b36dbb9b926a733cd4f2aebd68ed19fb15288.
@mnjs/utilstarball SHA-512: 009921feb011ab18c4861c65e422999d72cec7ce2696052bb6b413bb6eccde2649172fbd0335783297e4baafd7213358e45738bcb50cdb50690c12ff5a554ecd@mnjs/radiotarball SHA-512: 5c52ffba295a45fa148e4a8b332939d795bc6b2ec10c5ea60ea2bb9283b8f8e4b93b448000dc6331ddb016ff311d1f3b3f8dfcb302cb0d8586505954ce33903c marionette tarball SHA-512: a67a2adcd43221711e51a1f4540c8ec49e8460fb068562f8ae7855536b11a8af721e4e008f14570f2570448ad9cd8ab393853c167dfc0aa1b8259848f4d6b52f@mnjs/datatarball SHA-512: 98b6ad4dda52798a2ac1985b2ff333fafd71d564b3ce1aa693d7015db752469c1bfa683020d1de70bf4a5d80c34dfb9dfa11de7bff7de9eb0b58c83ea93a509b@mnjs/adapterstarball SHA-512: d475e3ed3bc013309490e08cb9c1e7cc3ed24af3fef3092b8ffb2469eff1d4ffe8c2acc84fb07cfc217357d7d34c404d9ebfc9683d337767c9f5882f0c4e26bcv5.1.0
Apparently, “optional” and “worth a minor release” are not opposites. Marionette 5.1 gives HTML templates and feature-owned routing a proper place in the stack. Two more opinions. Neither compulsory.
Marionette 5.1 brings two independently versioned companion packages into the recommended path for building new applications:
@mnjs/htmlprovides tagged-template rendering, incremental DOM updates, keyed lists, and directives, with a DOM API designed for Marionette-owned Views. Keep interactions inevents,triggers, andui; let the template describe the content.@mnjs/routerconnects named URLs with feature-owned routes and Application lifecycles. Features register their own routes, prepare their data, and manage their child Applications without moving every destination into one central routing file.- Updated guides and agent skills connect the first rendered View to composed and routed features, with executable examples and guidance for testing readiness, interactions, and teardown.
The coordinated packages
marionette,@mnjs/utils,@mnjs/radio,@mnjs/data, and@mnjs/adaptersmove to 5.1.0. HTML, Router, and the test helpers retain their independent versioning. The pre-v1 Router 0.1.1 updates its Catalog example to HTML and its Desk instructions to accept a compatible Adapters version instead of pinning 5.0.1. Its runtime and public API are unchanged; it is published separately from the five coordinated packages. Neither HTML nor Router becomes a required core dependency. Adapters’ core peer and Data’s nonoptional Utils peer now accept^5.0.1; core, Utils, and Radio keep their exact shared-runtime alignment. Data uses the shared Utils instance rather than installing a private copy.Existing compatible renderers, data integrations, and host routers remain
... (truncated)
Changelog
Sourced from marionette's changelog.
v5.1.1
We had barely finished saying “5.1.0” when Vite gave us a reason to say “5.1.1.” The runtime stayed put; the example tooling did not.
- Update Vite to 8.3.7 in the shipped Records example and locked tooling fixtures. Setup instructions select the current Vite 8 release and explain committing the resulting lockfile for reproducible installs. Vite is example/build tooling, not a Marionette runtime dependency.
- Refresh Router guidance for published
@mnjs/router0.1.1 and its passing Chromium, Firefox and Playwright WebKit coverage. Link the tested source archive and document native WebKit fragment/Back differences without changing routing behavior. The runnable companion example now checks Router 0.1.1 with published Marionette 5.1.0 and HTML 1.0.0.- Add Node 26 to required consumer LTS verification alongside Node 22 and 24. Check installed documentation recipes at each line's floor and latest patch; require Node 26 fixtures and recipes against the exact release candidate.
- Move the five coordinated packages
marionette,@mnjs/utils,@mnjs/radio,@mnjs/dataand@mnjs/adaptersto 5.1.1, with matching core/Radio/Utils dependencies. Data's nonoptional Utils peer and Adapters' core peer remain^5.0.1. HTML, Router and the test helpers keep their independent versions.Marionette runtime implementation and public APIs are unchanged from 5.1.0.
v5.1.0
Apparently, “optional” and “worth a minor release” are not opposites. Marionette 5.1 gives HTML templates and feature-owned routing a proper place in the stack. Two more opinions. Neither compulsory.
Marionette 5.1 brings two independently versioned companion packages into the recommended path for building new applications:
@mnjs/htmlprovides tagged-template rendering, incremental DOM updates, keyed lists, and directives, with a DOM API designed for Marionette-owned Views. Keep interactions inevents,triggers, andui; let the template describe the content.@mnjs/routerconnects named URLs with feature-owned routes and Application lifecycles. Features register their own routes, prepare their data, and manage their child Applications without moving every destination into one central routing file.- Updated guides and agent skills connect the first rendered View to composed and routed features, with executable examples and guidance for testing readiness, interactions, and teardown.
The coordinated packages
marionette,@mnjs/utils,@mnjs/radio,@mnjs/data, and@mnjs/adaptersmove to 5.1.0. HTML, Router, and the test helpers retain their independent versioning. The pre-v1 Router 0.1.1 updates its Catalog example to HTML and its Desk instructions to accept a compatible Adapters version instead of pinning 5.0.1. Its runtime and public API are unchanged; it is published separately from the five coordinated packages. Neither HTML nor Router becomes a required core dependency. Adapters’ core peer and Data’s nonoptional Utils peer now accept^5.0.1; core, Utils, and Radio keep their exact shared-runtime alignment. Data
... (truncated)
Commits
8e4b36dPrepare Marionette 5.1.1 (#3845)ec981e0fix(deps): patch Vite tooling and shipped example recipes (#3844)e5e8cf2Run Router tests across Chromium, Firefox and WebKit (#3837)9e3ea74Merge pull request #3838 from marionettejs/dependabot/npm_and_yarn/typescript...d9da9d2Merge current master into TypeScript ESLint patch update977cc9fMerge pull request #3840 from marionettejs/dependabot/npm_and_yarn/packages/h...1d96cacchore(deps-dev): bump the typescript-eslint group across 1 directory with 2 u...ba9f70bMerge master into HTML Rollup dependency update7689effMerge pull request #3839 from marionettejs/dependabot/npm_and_yarn/tooling-up...8c52f74chore: align Rollup measurement pins with 4.68.2- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions
Summary by cubic
Bumps marionette and @mnjs/adapters from 5.0.0 to 5.1.1. The runtime and public APIs are unchanged per upstream release notes, and the lockfile pulls @mnjs/radio and @mnjs/utils to 5.1.1 to stay aligned.
What to check
- 5.1.0 introduced optional
@mnjs/htmland@mnjs/routerpackages; neither is added here, so this app only picks up the coordinated core-version bump. - 5.1.1 is a patch over 5.1.0 containing only build-tooling and docs changes (Vite example, Node 26 verification).
@mnjs/adapters's peer dependency onmarionettewas relaxed from an exact5.0.0pin to^5.0.1; it still resolves to the pinned5.1.1here.marionettenow declares apackages/routerworkspace;node_moduleslayout in the lockfile changes accordingly.