Repository navigation
Update docs devDependencies (main) - #713
renovate[bot] wants to merge 1 commit into
Conversation
| "@iconify-json/octicon": "1.2.39", | ||
| "@shikijs/vitepress-twoslash": "3.23.0", | ||
| "@studiometa/playground-preview": "0.3.10", | ||
| "@studiometa/playground-preview": "0.4.0", |
There was a problem hiding this comment.
issue: Align playground preview with js-toolkit runtime
@studiometa/playground-preview@0.4.0 requires the js-toolkit v4 API, while this package still resolves @studiometa/js-toolkit to 3.9.0. The preview's v4 registration path is therefore incompatible with the docs runtime and can prevent playground components from rendering. Upgrade the js-toolkit dependency to the required v4 release, or keep the preview on a v0.3 version compatible with js-toolkit v3.
Confidence: high.
Reviewed by @weareikko/code-review v0.11.0 for commit 660c228.
Code ReviewRisk: Medium — issues that should be addressed before merge. This MR updates the documentation development dependencies, including the playground preview, build tooling, and VitePress packages. The playground preview major release requires js-toolkit v4, while the docs package still declares js-toolkit v3.9.0. 1 issue found:
Still open from earlier reviews (2 findings):
Review usage: 9,790 in (4,413 cached) / 525 out tokens — $0.0021 (openrouter/openai/gpt-5.6-luna, thinking: low) Reviewed by @weareikko/code-review v0.11.1 for commit a5f0994. Previous review runsPrevious run archived 2026-11-03T04:14:09ZCode ReviewRisk: High — blocking issues remain — resolve them before merge. Updates the documentation development dependencies, including the playground preview, VitePress, and related build tooling. The playground preview upgrade requires a corresponding major toolkit upgrade that this change does not include. 1 issue found:
Still open from earlier reviews (1 finding):
Review usage: 56,979 in (41,436 cached) / 1,454 out tokens — $0.0065 (openrouter/openai/gpt-5.6-luna, thinking: low) Reviewed by @weareikko/code-review v0.11.0 for commit 2155e50. Previous run archived 2026-10-28T14:41:42ZCode ReviewRisk: Medium — issues that should be addressed before merge. This change updates the documentation toolchain dependencies, including the playground preview, VitePress, and related build utilities. The playground preview major release requires js-toolkit v4, but the docs package still pins js-toolkit to 3.9.0. 1 issue found:
Review usage: 31,496 in (19,514 cached) / 785 out tokens — $0.0043 (openrouter/openai/gpt-5.6-luna, thinking: low) Reviewed by @weareikko/code-review v0.11.0 for commit 660c228. |
Export sizeBundled per export with peer dependencies left external, dynamic imports excluded and the output minified; sizes are gzipped. ✅ No export size changes. Unchanged (133)@studiometa/ui
@studiometa/ui-mapbox
@studiometa/ui-motion
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #713 +/- ##
=========================================
Coverage 86.32% 86.32%
Complexity 145 145
=========================================
Files 19 19
Lines 746 746
Branches 88 88
=========================================
Hits 644 644
Misses 95 95
Partials 7 7
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
660c228 to
2155e50
Compare
| "@iconify-json/octicon": "1.2.40", | ||
| "@shikijs/vitepress-twoslash": "3.23.0", | ||
| "@studiometa/playground-preview": "0.3.10", | ||
| "@studiometa/playground-preview": "0.4.0", |
There was a problem hiding this comment.
issue (blocking): Align js-toolkit with playground-preview 0.4
@studiometa/playground-preview 0.4.0 migrated to @studiometa/js-toolkit v4, but this package still pins @studiometa/js-toolkit to 3.9.0. The docs import and render the upgraded preview component, so this incompatible major-version combination can fail at runtime; update the toolkit dependency to the required v4 release or keep the preview package on the 0.3.x line.
Confidence: high.
Reviewed by @weareikko/code-review v0.11.0 for commit 2155e50.
2155e50 to
a5f0994
Compare
| "@iconify-json/octicon": "1.2.40", | ||
| "@shikijs/vitepress-twoslash": "3.23.0", | ||
| "@studiometa/playground-preview": "0.3.10", | ||
| "@studiometa/playground-preview": "0.4.0", |
There was a problem hiding this comment.
issue: Align js-toolkit with playground preview v0.4
@studiometa/playground-preview 0.4.0 requires consumers to use @studiometa/js-toolkit v4, but this package still declares 3.9.0 in dependencies. Using the upgraded preview with the existing toolkit can fail at runtime; upgrade the toolkit to the required v4 line or keep the preview on a compatible 0.3.x release.
Confidence: high.
Reviewed by @weareikko/code-review v0.11.1 for commit a5f0994.
This PR contains the following updates:
1.2.22→1.2.400.3.10→0.4.010.4.27→10.6.29.2.1→9.2.52.0.0-alpha.19→2.0.0-alpha.211.12.0→1.14.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
studiometa/playground (@studiometa/playground-preview)
v0.4.0Compare Source
Changed
@studiometa/js-toolkitv4 (^4.0.0-alpha.1, published on thenextdist-tag). The shipped shell calledcreateApp(), which v4 removed, so any consumer already on v4 gotTypeError: createApp is not a functionbefore the playground rendered anything. Registration is nowregisterComponent(Playground), and the page template declaresdata-component="Playground"on<body>so an instance exists because its element is in the document. Consumers must be on js-toolkit v4 (#79)createPlayground()no longer returns an application object — v4 has none. It configures the playground and registers the root component (#79)PlaygroundwatchesEditorVisibility,EditorsandIframewith$watchChildren()and pushes the editor visibility onto every instance it sees, including the ones that mount after it.Resizablewatches itsResizableSyncchildren the same way, and reaches the nearest one from a cursor with$closest()(#79)HtmlEditor,ScriptEditorandStyleEditordeclare their ownconfig.name. They used to inheritEditor's, which v4 would have registered under the wrongdata-componenttoken (#79)mounted()returns. v3 had no teardown at all (#79)Fixed
is-resizingstate from the drag service rather than from apointerupbound to the handle. A pointer released away from the handle never delivered that event, so the class stayed andis-resizing:pointer-events-noneleft the preview iframe unclickable (#79)ResizableSync.set()writes tostyle.width/style.heightrather than to non-existentwidth/heightelement properties, so a synchronised panel keeps its measured size (#79)v0.3.14Compare Source
Fixed
Package path ./<name>-loader.js is exported from package ... but no valid target file was foundon webpack 5.109+ (#77, d0c924a)esbuild-wasmfrom esm.sh at runtime instead of bundling it, fixing the brokenwasmURLthat stopped the preview from running the compiled script on webpack 5.109+, and keeping the ~11 MB wasm out of consumer bundles (#78, 89b55ae)v0.3.13Compare Source
Fixed
.jsimports to.d.tsinside emitted declaration chunks of self-hosted dependencies. rolldown-plugin-dts writes cross-chunk type imports with a.jsextension, but declaration chunks are content-hashed independently from the JS chunks, so./Foo-<hash>.jsnever existed on disk (only./Foo-<hash>.d.tsdid) — the editor's LSP fetched the dead.jsURL and type resolution broke for code-split subpathsv0.3.12Compare Source
Added
subpathsoption onDependencyConfig. For esm.sh dependencies,subpaths: truereads the package'spackage.jsonexports(disknode_modulesfirst, npm registry fallback) and adds each subpath to the import map as its own esm.sh URL, whilesubpaths: ['./utils']uses an explicit list. For local self-hosted dependencies,subpaths: truederives the multi-entry code-splitentriesfromexports(each subpath maps to its.tstarget), and is ignored when an explicitentriesmap is set (#75, 5c0c244)entriesmap onDependencyConfig. All subpaths of a workspace package (e.g. a barrel.and a lazy./manifest) are built together in one code-split tsdown build, so modules shared between entries are emitted once as a shared chunk and referenced by every entry — a single runtime instance, eliminating the singleton/identity hazard of bundling each subpath separately (#74)v0.3.11Compare Source
Fixed
import()no longer aborts the webpack build withConflict: Multiple assets emit different content to the same filename static/deps/<specifier>/index.js(#73, 39fbb2c)postcss/autoprefixer (autoprefixer)
v10.6.2Compare Source
/* autoprefixer: ignore next warning */(by @dualfroz).-webkit-cross-fade()for images with numbers (by @mkantautas).v10.6.1Compare Source
v10.6.0Compare Source
initial-lettersupport (by @thomasmattheussen).v10.5.6Compare Source
-webkit-gradients (by @ryanchou1994).v10.5.5Compare Source
v10.5.4Compare Source
v10.5.3Compare Source
v10.5.2Compare Source
-webkit-fill-availablebefore-moz-available, so Firefoxwill use
-webkit-version which is closer tostretch.v10.5.1Compare Source
grid-areaspan reset for overriding areas (by @puneetdixit200).v10.5.0Compare Source
mask-position-xandmask-position-ysupport (by @toporek).open-cli-tools/concurrently (concurrently)
v9.2.5Compare Source
What's Changed
Full Changelog: open-cli-tools/concurrently@v9.2.4...v9.2.5
v9.2.4Compare Source
Full Changelog: open-cli-tools/concurrently@v9.2.3...v9.2.4
v9.2.3Compare Source
shell-quote- #591, #596vuejs/vitepress (vitepress)
v2.0.0-alpha.21Compare Source
Bug Fixes
Features
v2.0.0-alpha.20Compare Source
Bug Fixes
Features
./) andassetsBase(CDN prefix) (#5406) (feadd9f)$frontmatterexpressions while rendering markdown (#5412) (a1eb284)throwUnhandledErrorInProduction(#5419) (a6573ff)okineadev/vitepress-plugin-llms (vitepress-plugin-llms)
v1.14.0Compare Source
🚀 Enhancements
themeConfig(#145) - by @mgigirey (fd96c)🩹 Fixes
💖 Contributors
View changes on GitHub
v1.13.5Compare Source
🩹 Fixes
hintBlockdiv attributes (#141) - by Divyansh Singh (75bf0)💖 Contributors
View changes on GitHub
v1.13.4Compare Source
🩹 Fixes
💖 Contributors
View changes on GitHub
v1.13.3Compare Source
🩹 Fixes
ES2023array methods.toSorted()and.toReversed()for Node 18 compatibility (#135) - by @suyi91, and@okineadev (50fd1)💖 Contributors
View changes on GitHub
v1.13.2Compare Source
🩹 Fixes
data-nosnippettohintBlockmarkup (#134) - by @KamikX (4110a)💖 Contributors
View changes on GitHub
v1.13.1Compare Source
No significant changes
View changes on GitHub
v1.13.0Compare Source
🚀 Enhancements
💖 Contributors
View changes on GitHub
v1.12.2Compare Source
🚀 Enhancements
💖 Contributors
View changes on GitHub
v1.12.1Compare Source
🩹 Fixes
.d.tstypes forvitepress-componentsmodule too - by @okineadev (c1577)💖 Contributors
View changes on GitHub
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.