Repository navigation
Runic SDK 0.21.0
Pre-releaseRunic SDK 0.21.0
Install matching 0.21.0 packages from NuGet and npm;
Runic.Application.Views.CsWebUi is 0.21.0-preview.1.
Tested with Runic Translations 0.13.0 and Runic Command Line 0.13.0.
0.21.0 brings your IDE's JavaScript debugger to the page on every operating
system. On Linux, dotnet runic dev serves the Window's WebKitGTK page to
JavaScript debuggers through a Chrome DevTools Protocol adapter, so VS Code
stops at breakpoints in the frontend's sources as it does with WebView2 on
Windows (#1029, preview). dotnet runic dev --browser serves the Window to
Chrome or Edge instead, so the page's JavaScript can be debugged in the IDE on
macOS too (#1053).
The browser's own developer tools learn about Runic: React DevTools labels the
hooks' values and Vue DevTools gets a Runic Views inspector (#1041), the
console shows View clients and states readably (#1042), WebView2 windows open
their DevTools window from code and load DevTools extensions in Development
(#1056), and dotnet-runic ships a Runic panel for the developer tools,
which dotnet runic dev loads into the Window's WebView2 on Windows and which
Chrome and Edge load unpacked (#1060). All of it is development-only.
Hosted application windows (experimental) give a GTK 4 window back to the user
after a menu-bar choice (#1045) and treat a Linux guest that holds capabilities
as elevated (#1047). The development endpoints are hardened: the Vite plugin's
/__runic/* endpoints and HMR events answer only admitted clients (#1052), and
WebView2's debugging endpoint opens only in Development (#1071), as WebKit's
remote inspector did in 0.20.
0.21.0 also carries the API review before 1.0: .NET members added since 0.12
are renamed so that one feature uses one word, trusted component mode moves to
the npm packages' ./experimental entries, two development formats take dotted
names, and internal MSBuild names start with _Runic. The 0.21 release train is
Runic Translations 0.13.0, runic-sdk 0.21.0 and the Runic editor extensions
0.21.0; Runic Command Line stays at 0.13.0. These changes need edits in an
application: Upgrading from 0.20 lists them, and the
migration guide
collects them.
Highlights
- JavaScript debugging on Linux
(preview): VS Code's JavaScript debugger attaches to the Window's WebKitGTK
page underdotnet runic dev, with breakpoints in the frontend's sources,
also in code that runs while the page loads. dotnet runic dev --browser:
the IDE debugs the Window's page in Chrome or Edge on every OS, with the
template's newWindow in Chromelaunch configuration.- DevTools integrations, development-only:
a Runic panel in the developer tools of Chrome, Edge and the Windows Window,
Runic state in React DevTools and Vue DevTools,
readable View clients in the console and
WebView2's DevTools window and DevTools extensions. - Hosted application windows (experimental): on GTK 4 a menu-bar choice gives
a guest's window back to the user, and a Linux guest with capabilities counts
as elevated (Fixes,
Behaviour and output changes). - Development endpoints hardened: vite-plugin-runic's
/__runic/*endpoints
and HMR events answer only admitted clients, the Linux debugging endpoints
admit only the developer's user, and WebView2's debugging endpoint opens only
in Development (Behaviour and output changes). - The API review before 1.0: consistent .NET names, trusted component mode in
./experimental, dotted format IDs and_RunicMSBuild internals
(Breaking changes), and
selection paths, Angular's text locale and field types.
Upgrading from 0.20
Update every Runic NuGet and npm package to 0.21.0 together and rebuild, so that
the generated clients and Bridges are regenerated. The Views protocol and its
features are unchanged, so a 0.20 page and a 0.21 host still connect.
Most applications change only a few calls. Rename the .NET members of the
API review that the application uses; the compiler lists
each one, and saved navigation paths and every wire format load unchanged. A
hosted guest in trusted component mode imports it from ./experimental
(Experimental features). A tool or a
test that reads Runic's development endpoints from another machine, or reads
sources.json, checks the behaviour changes
and the format IDs. Runic's VS Code extension reads the
development source map's new format ID from the Runic editor extensions 0.21.0
on; update it with the SDK.
- Runic Translations 0.13 (the 0.21 train candidate).
Runic.Application.Views.Translationsrequires Runic Translations
[0.13.0, 0.14.0), so an application that uses it moves every Translations
package, NuGet and npm, to 0.13.0. The template pins Translations 0.13.0 three
ways: thedotnet-runic-translationstool,Runic.Translationsand
.Build, and@runic-artifex/vite-plugin-runic-translations. Translations
0.13 renamesTranslationContextBuilder.AddtoAddCatalog: replace.Add(
with.AddCatalog(where aTranslationContext.CreateBuilder()chain
registers a catalog, as the template'sWorkspaceServices.csnow does. The
in-page editing API reads onlyRUNIC_DEV_ALLOW, which vite-plugin-runic
reads too;RUNIC_TRANSLATIONS_EDIT_ALLOWis ignored. Runic Command Line
stays at 0.13. See the
Translations 0.13.0 notes.
Breaking changes
-
.NET API names from the 0.21 API review. Members added since 0.12 are
renamed so that one feature uses one word. Rename the calls; nothing else
changes, and the wire formats stay:NavigationPath.ToJsonand
NavigationSelectionPath.ToJsonstill write a selection's index as
"selected"(format version 1), so saved paths load unchanged.Package 0.20 0.21 Runic.DesktopIDesktopWindowBoundsHostIDesktopBoundsWindowHostRunic.DesktopIDesktopWindowShowStateHostIDesktopShowStateWindowHostRunic.DesktopDesktopWindowCapabilities.WindowPlacementDesktopWindowCapabilities.Placement(same value)Runic.DesktopDesktopHost.NoteRecentDocumentAsync(path)DesktopHost.AddRecentDocumentAsync(path)Runic.NavigationNavigationSelectionPath.SelectedNavigationSelectionPath.SelectedIndexRunic.Application.TestingRunicRegionCollectionState.SelectedRunicRegionCollectionState.SelectedIndexRunic.Application.ViewsRunicWindowOptions.MaximumWindowUploadBytes,WindowContentSessionOptions.MaximumWindowUploadBytesMaximumPendingUploadBytesRunic.Application.ViewsRunicWindowsChangedEventArgs.Opened(bool) and itsbool openedconstructor parameterRunicWindowsChangedEventArgs.Change, an open enumRunicWindowsChange(Opened,Closed):args.Openedbecomesargs.Change == RunicWindowsChange.OpenedRunic.Application.ViewsRunicUpload.SaveAsAsync(path, overwrite)RunicUpload.SaveToFileAsync(path, overwrite)Runic.Application.TestingRunicServeOnlyTestPlatform.EnqueueOpenFile,EnqueueSaveFile,EnqueueOpenDirectory,EnqueueFileDialogDismissed,EnqueueFileDialogUnavailable,EnqueueFileDialogFailedplatform.FileDialogs.EnqueueOpen,EnqueueSave,EnqueueOpenDirectory,EnqueueDismissed,EnqueueUnavailable,EnqueueFailedRunic.Application.TestingRunicServeOnlyTestPlatform.EnqueueMessageBoxAnswerplatform.MessageBoxes.EnqueueAnswerRunic.Application.TestingRunicServeOnlyTestPlatform.EnqueueContextMenuChoice,EnqueueContextMenuDismissedplatform.ContextMenus.EnqueueChoice,EnqueueDismissedRunic.Application.TestingRunicServeOnlyTestPlatform.SetClipboard,SetClipboardTextplatform.Clipboard.SetContent,SetTextThe serve-only fakes now have the names of
RunicTestPlatform's, so a test
moves between the in-process host and serve-only unchanged. The host-wide
default of the pending-upload limit is new:MaximumPendingUploadByteson
RunicDesktopHostOptions,RunicCsWebUiHostOptionsand
RunicWindowTestHostOptions, besideMaximumUploadBytes. Only a custom
Runic Desktop window host implements the two renamed interfaces. -
Two development file formats take dotted names, like every other Runic
format identifier (runic.views.fields/2,runic.application.tool.dev-session/1):
the Bridge generator's development source map (obj/…/runic-bridge/sources.json,
which/__runic/sourcesserves and the session file'ssourceMapnames) is
runic.views.bridge-sources/1instead ofrunic-bridge-sources/1, and the
handler analysis that/__runic/handlersanswers (RunicHandlerAnalysis.format
of@runic-artifex/vite-plugin-runic) isrunic.vite.handlers/1instead of
runic-handlers/1. The content is unchanged.@runic-artifex/vite-plugin-runic
still reads a map with the old name through 0.21 and serves it with the new
one; a tool of its own that readssources.jsonor/__runic/sourcesaccepts
the new name. -
Internal MSBuild names start with
_Runic. Twelve names that the packages
use internally, but that looked like settings, now have the prefix of the other
internal names: the targets_RunicDesktopValidateServer,
_RunicDesktopValidateNativeServer,_RunicDesktopResolveNativeServer,
_RunicDesktopLinkNativeServer,_RunicDesktopRemoveLinkedNativeServer,
_RunicDesktopRequireRepositoryNativeServer,
_RunicNativeServerRequireStaticLibraryand
_RunicAssetsVerifyEmbeddedArchive, and the properties
_RunicDesktopKestrelReferenced,_RunicDesktopNativeServerReferenced,
_RunicNativeServerArtifactsand_RunicNativeServerRuntime(each formerly
without the leading underscore). MSBuild properties and items
now says that the targets of the Runic packages are not settings, apart from
the three documented extension pointsRunicViewsGenerateBridge,
RunicViewsBuildFrontendandRunicViewsCopyFrontend: a project that ran a
target of its own withBeforeTargetsorAfterTargetson one of the renamed
targets hooks it onto an MSBuild target instead. No documented setting
changed, and Runic.Desktop still reads the server packages' markers of 0.20
through 0.21.
Behaviour and output changes
-
A Linux guest that holds capabilities runs elevated (hosted applications,
experimental,RUNICDESK103). On Linux a guest that holds capabilities
without running as root, a non-empty effective or
permitted set (CapEff,CapPrmin/proc/self/status, such as from
setcapor ambient capabilities), now runs elevated. It refuses hosted mode
withguest-elevated, and with both opt-ins with
guest-elevated-host-not-elevated, since the elevated pair needs a root
parent. In a root elevated pair, the parent's capability sets must now hold
every capability the guest holds
(#868,
#1047). -
vite-plugin-runic's development endpoints admit fewer clients.
In@runic-artifex/vite-plugin-runic,/__runic/stateand
/__runic/diagnosticsnow answer only loopback and the hosts and networks ofrunic({ allow })/
RUNIC_DEV_ALLOW, and/__runic/staterefuses pages of another origin.
Runic's HMR events are ignored from other clients, and the development state
is sent only to admitted clients. Withserver.allowedHosts: true, Runic's
endpoints and HMR connections checkHostthemselves (IP addresses,
localhost, allow-listed names). On Linux, open-in-editor accepts a loopback
client only when it belongs to the user running the dev server; macOS and
Windows log that they cannot tell local users apart. A tool that read
/__runic/statefrom another machine needs that machine in the allow list. -
Kept View clients stay on their own Bridge. A client that a framework
binding keeps for itskeepAliveperiod is taken over only while its instance uses the Bridge it connected over. After a new
__runicBridge(a new mock Bridge, or a page runtime replaced at runtime) the
next binding connects to the new Bridge and the kept client is released;
installMockBridgereleases it at once
(@runic-artifex/viewsREADME, "Client lifetime";
#1058). -
WebView2's debugging endpoint opens only in Development on Windows
(#1071). WebView2
opened a DevTools Protocol endpoint whenever
WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTSheld--remote-debugging-port, also
with developer tools off, so a release could be scripted through it. Now,
unlessDOTNET_ENVIRONMENT(or elseASPNETCORE_ENVIRONMENT) is
Development, the WebView2 host removes the variable before it creates its
WebView2 environment, also whenDevToolsistrue. Its other switches no
longer apply outside Development either, and processes the application starts
after that no longer inherit it. Arguments the application passes in
DesktopWindowOptions.BrowserArgumentsare not changed. To debug a build
this way, run it withDOTNET_ENVIRONMENT=Development.
Experimental features and how to opt in
Nothing changes for an application that does not use them. Each .NET family is
a compile error until the project suppresses its ID
(experimental APIs),
and an npm API is exported only from its package's ./experimental entry.
Hosted applications (RUNICDESK103), the side panel (RUNICDESK104) and the
close drain (RUNICDESK105) stay experimental in 0.21, with these changes from
the API review:
-
Hosted applications, side panel and close drain: API review changes
(RUNICDESK103,RUNICDESK104,RUNICDESK105). The host protocol's wire
tokens, such as the dialog kindsfolderandfolder-multipleand the
region-detachreasons, stay unchanged.ID 0.20 0.21 RUNICDESK103RunicHostedDialogKind.OpenFolder,OpenFolders;RunicTestDialogKind.OpenFolder,OpenFoldersOpenDirectory,OpenDirectories, asIFileDialogsnames themRUNICDESK103RunicHostedWindow.PresentationRunicHostedWindow.DesktopWindowRUNICDESK103RunicHostedRegion.DetachAsync,MoveToAsyncreturnTask;SetAppearanceAsyncreturnsTask<bool>ValueTaskandValueTask<bool>, asRequestCloseAsync. A caller that stores the task calls.AsTask()RUNICDESK103RunicHostedRegionEventArgs.Reasonis astring("removed","reload","crashed","host","closed")An open enum RunicHostedRegionDetachReason(Removed,Reload,Crashed,Host,Closed)RUNICDESK103RunicTestDialogRequest.Kind(the wire kind, astring) besideDialogKindKindis theRunicTestDialogKind;DialogKindis removedRUNICDESK103RunicTestPresentationRequest.Kindis the wire kind, astring("set-full-screen")An open enum RunicTestPresentationKind(SetFullScreen)RUNICDESK104No DesktopSidePanelRefusal.Closed; a window that closed whileOpenSidePanelAsyncran threwObjectDisposedExceptionDesktopSidePanelRefusal.Closed, asRunicSidePanelRefusal.Closed:OpenSidePanelAsync,MoveToEdgeAsyncandSetWidthAsyncrefuse with it when the window or the panel closes while they run. A window or panel closed before the call still throwsObjectDisposedExceptionRUNICDESK105RunicCloseDrain.KeepsWindowRunicCloseDrain.KeepWindow -
Trusted component mode moved to
./experimental(RUNICDESK103). Its npm
side was the stable-looking@runic-artifex/views/componententry and the
componentoption ofrunic(), although the mode is experimental. Before 1.0
an experimental npm API is exported only from./experimental, so 0.21 removes
the./componententry without a deprecated alias:- Import
defineRunicComponent,connectComponentBridgeand the
RunicComponent*types from@runic-artifex/views/experimentalinstead of
@runic-artifex/views/component. - In
vite.config.ts, importrunicfrom
@runic-artifex/vite-plugin-runic/experimentalto use
runic({ component: { entry, name } }); it takes the root entry's options
too. The root entry'srunicnow throws forcomponent, and no longer
exportsRunicComponentOptions, which the experimental entry exports with
RunicExperimentalViteOptions.
- Import
JavaScript debuggers attach to the Window on Linux (#1029, preview)
On Linux, dotnet runic dev serves the Window's WebKitGTK page to JavaScript
debuggers on port 9222, as WebView2 does on Windows, through a Chrome DevTools
Protocol adapter for WebKit's remote inspector. VS Code's JavaScript debugger
attaches with the runic-app template's Attach to the page (JavaScript)
configuration, now one for Windows and Linux: breakpoints in the frontend's
sources through the development server's source maps, stepping, conditions,
logpoints, exceptions, the console and the page's variables, also after a
reload, an HMR update or a Window restart under dotnet watch, and in code that
runs while the page loads, as with Chromium.
Window + WebKitGTK (Linux) starts the Window under the .NET debugger with
dotnet runic dev --no-window and attaches it too. GTK 3 (WebKitGTK 4.1) and
GTK 4 (WebKitGTK 6.0), X11 and Wayland.
When another local client, such as GNOME Web's inspector:// page, takes
WebKit's inspector during a session, the debugger learns that its page detached,
as from Chrome when another DevTools takes over, dev names the cause, and
attaching again continues; the Window keeps running.
The endpoint listens on loopback only, refuses requests with an Origin or a
Host that is not an IP address or localhost, closes connections of other
local users, and runs only under dev. The adapter connects only to a WebKit
inspector port of the same user. WebKit's inspector:// port is open to other
local users, also while a debugger is attached: on a shared machine, use
--no-debug-endpoint.
[dev] Debugging: and the session file's debugEndpoints
("engine": "webkitgtk", "protocol": "cdp") name it, next to WebKit's
inspector:// server, which GNOME Web opens while no debugger is attached.
--no-debug-endpoint turns both off; --webkit-inspector opens WebKit's own
Web Inspector over HTTP instead, on WebKitGTK 2.54.3 or later within 2.54, or
2.56 or later (WebKit bug 330602). dev warns about a
WEBKIT_INSPECTOR_HTTP_SERVER of your own on an unfixed WebKitGTK, and about
inspector addresses that are not loopback. When 9222 is taken, dev moves the
adapter to a free port and names it, except under --no-window, whose IDE
attach configuration names 9222: there it stops with RAPPDEV1017.
RUNIC_DEV_CDP_TRACE leaves script sources and other long strings out unless
RUNIC_DEV_CDP_TRACE_SOURCES=1. The adapter is a preview until its CI job has
run through a release; Rider is not verified yet. See
Debug the page's JavaScript on Linux.
Debug the page in Chrome on every OS: dotnet runic dev --browser (#1053)
dotnet runic dev --browser serves the Window without a native window (its
serve-only mode, RUNIC_APPLICATION_SERVE_ONLY=1) and lets your IDE's
JavaScript debugger open its page in Chrome or Edge at http://127.0.0.1:9224/,
which dev redirects to the Window's own address. Breakpoints in the frontend's
sources then stop in the IDE on Linux and macOS too, where the Window's engine
is WebKit; on macOS it is the only IDE route. The runic-app template's new
Window in Chrome launch configuration (--editor vscode) runs it, with a
runic: dev --browser task. The page runs on Chromium, not the Window's engine,
and without native window features: file dialogs and menus report
OwnerUnavailable.
[dev] Browser: Window serves at <url> names the address, and the session
file's new browser property lists it and each served Window; [dev] Ready
follows the Window's first page. The Window's own address carries its
credential, so dev prints neither it nor the serve-only lines. The address
redirects only navigations the browser starts itself (no Origin, a
Sec-Fetch-Site of none or same-origin, an IP or localhost Host), and
on Linux only from the user who runs dev; macOS and Windows cannot tell a
loopback connection's user. Open it again after dotnet watch restarts the
Window. --browser cannot be combined with --no-window or
--webkit-inspector; without a free loopback port it fails with RAPPDEV1016. See
Debug the page in Chrome.
A Runic panel in the developer tools of Chrome, Edge and the Windows Window (#1060)
dotnet-runic ships an unpacked Chrome DevTools extension (Manifest V3, no
Chrome Web Store listing). Its Runic panel lists the page's Views with
their C# ViewModels, revisions and state, and the recent Bridge calls with
their kind, outcome, time, C# member and, from a .NET host in Development, the
C# handler's name and duration; C# locations open in the editor through the
development server. Its Runic pane in the Elements panel describes the
selected element as Runic Inspect does: component, bound members, commands
with their C# handlers, recent calls and texts. dotnet runic dev prints the
extension's folder ([dev] DevTools extension:) and writes it to the session
file as devtoolsExtension. On Windows, dotnet runic dev loads it into the
Window's WebView2 in Development by adding it to
RUNIC_DESKTOP_DEVTOOLS_EXTENSIONS after any folders you list there;
--no-devtools-extension leaves it out. In Chrome or Edge, including the
browser that dotnet runic dev --browser's launch opens, load it with Load
unpacked on chrome://extensions, as dev prints; branded Chrome ignores
--load-extension, which Chromium and Chrome for Testing still take. It reads
the page through Runic Inspect's new snapshot() and describe($0), which exist only under the development
client, so production pages are unchanged. See
The Runic DevTools extension.
Runic state in React DevTools and Vue DevTools (#1041)
In development, the React hooks label their values in React DevTools' hooks
pane: useView shows the View (EditorViewModel · editor · rev 12),
useField the field's state (title = "Draft" · editing · 1 error),
useCommand, useOperation and useLatestOperation their status
(running 40%, failed: …). React computes a label only while DevTools shows
the component.
With Vue DevTools on the page, @runic-artifex/vue adds a Runic Views
inspector that lists the page's Views with their state and last calls, and a
Runic Bridge calls timeline layer. It loads @vue/devtools-api 8, a new
optional peer dependency, only when Vue DevTools is present.
@runic-artifex/react and @runic-artifex/vue now have a development build
like @runic-artifex/views (the development export condition): production
builds contain none of this. The state inspector channel's state event also
carries the View's contract. See
React DevTools and Vue DevTools.
Readable View clients and states in the console (#1042)
In development, @runic-artifex/views registers custom object formatters, so
Chromium's and Firefox's console and Sources panel show a View client as
EditorViewModel · editor · rev 12, its state as
EditorViewModel state · rev 12 {title: "Draft", …} and a field controller's
state as title = "Draft" · editing, each expanding into its parts. Turn on
Enable custom formatters in the DevTools settings once. The production
build has no formatter. See
Custom object formatters.
WebView2 DevTools window and DevTools extensions in Development (#1056)
DesktopWindow.OpenDevToolsAsync opens WebView2's DevTools window from code,
and a WebView2 window whose developer tools are on has an Open DevTools item
in its system menu (Alt+Space). The call returns false where the developer
tools are off, as in production, and on other engines.
DesktopHostOptions.DevToolsExtensions, and the
RUNIC_DESKTOP_DEVTOOLS_EXTENSIONS variable for one session, list unpacked
browser extensions, such as React Developer Tools or Vue.js devtools, that
WebView2 windows install into their profile before the first page loads. Only
in Development does the WebView2 environment enable extensions; outside it the
list is ignored. An extension Runic installed whose folder is no longer listed is
removed from the profile in Development. A folder WebView2 rejects is reported as
devtools-extension-failed. See
the debugging guide.
Selection paths, Angular text locale and field types (#1064)
NavigationSelectionPath.ToJson()andFromJson(string)save and read one
selection, such as a tab strip, without the rest of the navigator, in the
format ofNavigationPathandNavigationRegionPath: the sameversion,
bounds andFormatExceptions. Restore it with the selection'sRestoreAsync.@runic-artifex/angularhasinjectTextLocale({ injector }), the
textLocaleSignalof the injection context's Runic instance, like its other
inject*functions.textLocaleSignalstays for code outside one.@runic-artifex/angularre-exports the field types itsinjectFieldand
injectFormsignatures use, as the React, Vue and Svelte adapters do:
BridgeField,BridgeFieldConstraints,BridgeFieldKind,FieldBaseline,
FieldDefinition,FieldError,FieldErrorKindandFieldState.- The
dotnet runic devIDE contract now includes the[dev] Evaluatingand
[dev] Reloadingline prefixes, which the template's.vscode/tasks.json
waits on. Environment variables
lists theRUNIC_*variables.
Fixes
- New SvelteKit apps from the
runic-apptemplate (with or without
--translations) get@sveltejs/adapter-static4.0.1, which fixes
GHSA-jf9x-2fg2-hx4w.
The advisory concerns route config generated for Vercel; an existing app can
move to 4.0.1, which@runic-artifex/sveltekit's peer range already admits
(#1040). - Hosted application windows (experimental,
RUNICDESK103): on GTK 4, choosing
an item of a window's native menu bar, by pointer or with the bar's own
keyboard navigation, or of the desktop's global menu now gives a window the
application activated back to the user, as on Windows, macOS and WebKitGTK 3.
Before, the application's clipboard and launch requests from that window
stayed refused until the user switched away and back or dropped files onto it
(#855,
#1045). - VS Code's JavaScript debugger no longer reports "Could not read source map"
for@runic-artifex/vite-plugin-runic'sdist/inspect-frameworks.json
every attach: a doc comment in it read as the file's source map comment.
Package verification now rejects such comments in every Runic npm package
(#1050). - A client that
useVieworinjectViewkeeps after its component went away is
no longer taken over by the next test's binding when each test installs a new
mock Bridge: it kept talking to the previous test's mock, so the new test's
commands reached the old handlers and its state never arrived. A kept client
is now taken over only while its instance uses the Bridge it connected over,
andinstallMockBridgereleases the previous Bridge's kept clients at once.
releaseKeptViews()from@runic-artifex/views/mockreleases the kept
clients for a suite that keeps one Bridge across tests
(#798,
#1058). - Runic Inspect no longer loses a click on a card link when the page's text
changes during the click: the card now keeps its unchanged links and updates
only what changed, instead of drawing all of its contents again
(#1063). - New SvelteKit applications (
dotnet new runic-app --frontend sveltekit)
get@sveltejs/kit3.1.1, which fixes a crash of adapter-node's server on a
malformed URL withreroute
(GHSA-mw6w-2fmv-pvw3).
The template's static output never ran that code, so existing applications
aren't affected; move to 3.1.1 to keepnpm auditquiet
(#1074).
CI and tests
- A new
WebKitGTK debugging / js-debugjob attaches VS Code's JavaScript
debugger (vscode-js-debug's DAP server) throughdotnet runic dev's adapter
to therunic-apptemplate's Window, GTK 3 and GTK 4, and runs the same
scenarios through theWindow in Chromeconfiguration (#1033, #1053). - The train compatibility gate serves the Translations npm candidates to the
template scenarios, and picks the newest successfulmainrun from the
unfiltered run list, which GitHub's filtered listing could omit for over an
hour (#1036, #1075). - When a run builds only one runtime identifier's native server library and
takes the others from the cache, the check that every runtime identifier has
its libraries finds the one downloaded artifact, whichdownload-artifact
extracts without its directory (#1039). - A pull request that changes only Markdown, such as a package README, plans no
Windows or macOS leg. It still runs the Linux jobs, because package READMEs are
packed. The analyzers'AnalyzerReleases.*.mdfiles are compiler inputs and
keep their legs (#1048). tests/native/Runic.Desktop.GlobalMenuCheck, a manual check app for the Linux
global menu (#1049).- Runic Inspect's browser test no longer flakes when a card redraw splits the
click that opens a message (#1054, #1061). - The
windows-11-armjobs close the runner's full-screen Microsoft account
prompt, which broke the notification area and OLE drags, so the status icon
check runs on win-arm64 too (#373, #391, #1066). - The template tests bind a train candidate's integrity in every lock format,
not onlypackage-lock.json: the pnpm and Bun variants no longer fail with a
tarball integrity error when an upstream repository's candidate is rebuilt
with the same version during a release train (#1076).
Known issues
- WebKit's own
inspector://port is open to other local users. Under
dotnet runic devon Linux, WebKitGTK's remote inspector server, which the
debugging adapter and GNOME Web connect to, cannot be filtered: another local
user can connect to it, also while a debugger is attached, and a client that
replaces another one can crash the Window on WebKitGTK 2.54. The adapter
detaches its debugger when it notices a replaced client. On a shared machine,
rundotnet runic dev --no-debug-endpoint. See
Debug the page's JavaScript on Linux. - WebKitGTK's HTTP inspector accepts any website's
OriginandHostbefore
2.54.3 within 2.54, and before 2.56
(WebKit bug 330602); the
newest release, 2.54.2, is affected. Outside Development the variable is
cleared (0.20); underdotnet runic dev,--webkit-inspectoropens it only
on a fixed WebKitGTK, anddevwarns about aWEBKIT_INSPECTOR_HTTP_SERVER
of your own on an unfixed one. Use the debugging adapter or
WEBKIT_INSPECTOR_SERVERinstead. - IDE JavaScript debugging is a preview on Linux and goes through Chrome on
macOS. The Linux adapter stays a preview until its CI job has run through a
release, and Rider's JavaScript debugger is not verified with it. WKWebView
opens no DevTools Protocol endpoint, so on macOS the IDE debugs the page in
Chrome withdotnet runic dev --browser, without native window features, or
Safari's Web Inspector debugs the Window. On Windows, WebView2 ignores the
endpoint's variable in an elevated Window: rundevand the IDE without
elevation. - 0.20.0's known issues about the Angular CLI (no Vite plugins, so no dock and
no in-place message updates), Go to Type Definition on the result of
connect…()and CS-WebUI dropping the query of a request for/
(cs-webui#33), and
0.19.0's about the side panel, the close drain on an installed browser,
serve-only mode and CS-WebUI, assistive technologies in hosted regions and a
guest'sprefers-color-schemein a region, are unchanged; see
0.20.0's known issues.
What's Changed
- Train gate: serve the Translations npm candidates to template scenarios by @ViktorJannicke in #1036
- Record the 0.20.0 publication; main is 0.21.0 by @ViktorJannicke in #1038
- IDE debugging on Linux: a CDP adapter for WebKitGTK under dotnet runic dev (preview) (#1029) by @ViktorJannicke in #1033
- Native server libraries: accept one downloaded artifact without its directory by @ViktorJannicke in #1039
- adapter-static 4.0.1 (GHSA-jf9x-2fg2-hx4w) by @ViktorJannicke in #1040
- CI: plan no Windows or macOS leg for Markdown-only changes by @ViktorJannicke in #1048
- WebKitGTK debugging: admit only the developer's user on the debugging endpoints by @ViktorJannicke in #1046
- GTK 4: menu-bar choices give a guest-activated window back to the user (#855) by @ViktorJannicke in #1045
- Hosted applications: count Linux capabilities as elevated for a guest (#868) by @ViktorJannicke in #1047
- Kept view clients are taken over only on their own Bridge by @ViktorJannicke in #1058
- Keep Runic Inspect's card links through a refresh (#1062) by @ViktorJannicke in #1063
- Release guide: rechecks before each release by @ViktorJannicke in #1068
- Add the 0.21 API review's additive items by @ViktorJannicke in #1064
- Add a manual check app for the Linux global menu by @ViktorJannicke in #1049
- vite-plugin-runic: access list for state and HMR events, Host check, open for the server's user by @ViktorJannicke in #1052
- API review for 0.21: component mode in ./experimental, dotted format IDs, _Runic MSBuild internals by @ViktorJannicke in #1067
- Runic DevTools extension: a Runic panel and an Elements pane, shipped unpacked (#1044) by @ViktorJannicke in #1060
- CI: close the windows-11-arm Microsoft account prompt; run the status icon on win-arm64 by @ViktorJannicke in #1066
- WebKitGTK debugging: --no-window keeps port 9222, a smaller CDP trace, and WebKit's inspector client handling in the docs by @ViktorJannicke in #1070
- WebView2: no DevTools Protocol endpoint from the environment outside Development by @ViktorJannicke in #1071
- vite-plugin-runic: no source map comment in shipped JavaScript (#1050) by @ViktorJannicke in #1055
- WebKit CDP adapter: an instrumentation pause per script, before it runs (#1051) by @ViktorJannicke in #1072
- 0.21 API review: .NET renames (API-03 to API-14) by @ViktorJannicke in #1069
- Fix flaky Runic Inspect message open in inspect.browser.test (#1054) by @ViktorJannicke in #1061
- 0.21 train candidate: build against Translations 0.13.0 (T) by @ViktorJannicke in #1074
- React DevTools labels and a Vue DevTools inspector (#1041) by @ViktorJannicke in #1057
- Custom object formatters for View clients and states (#1042) by @ViktorJannicke in #1059
- Leave the 0.21 train feed: nuget.org lock hashes, published Translations Vite plugin in the template locks, every lock format bound in the template tests by @ViktorJannicke in #1076
- WebView2: DevTools window and DevTools extensions in Development (#1043) by @ViktorJannicke in #1056
- WebKit CDP adapter: survive another client taking WebKit's inspector (D068.1) by @ViktorJannicke in #1073
- Train gate: pick the newest successful main run from the unfiltered run list by @ViktorJannicke in #1075
- dotnet runic dev --browser: debug the page in the IDE's Chrome on every OS (#1031) by @ViktorJannicke in #1053
- Runic DevTools extension: load it into the Windows Window's WebView2, explain it under --browser (D068.3) by @ViktorJannicke in #1078
- 0.21.0 notes and migration guide by @ViktorJannicke in #1077
Full Changelog: v0.20.0...v0.21.0