@solidrt/router 0.0.65 → 0.0.66

package/AGENTS.md

@@ -157,4 +157,4 @@ export function SettingsRoutes() {
   `/a/b`) and an http(s) host.
 - Tooling: `open_link` / `POST /__control__/link` opens a screen,
   `get_location` / `GET /__control__/link` reads the path the router
-  publishes, `srt render --link <path>` renders that screen.
+  publishes, `sol render --link <path>` renders that screen.

package/README.md

@@ -2,7 +2,7 @@
 
 `@solidrt/router` makes screens addressable. A route tree maps a path like
 `/settings/theme` to a screen, a stack holds where the app is, and the same
-path is what a link from the OS, an MCP tool, `srt render --link` or a saved
+path is what a link from the OS, an MCP tool, `sol render --link` or a saved
 session carries. It is a layer over core: core reports links (`onLink`,
 `env.launchLink`) and the back intent (`onBack`), the router decides what
 they mean. An app can route by hand without it.
@@ -104,7 +104,7 @@ export function SettingsRoutes() {
 </Route>
 ```
 
-`srt init` with the router selected starts a project in this shape.
+`sol init` with the router selected starts a project in this shape.
 
 ## Params are validated
 
@@ -286,9 +286,9 @@ is dropped. A link that matches nothing lands on the catch-all route, or is
 ignored with a warning.
 
 `<Router>` reports the current path through `reportLocation` from
-`srt:dev`, so `GET /__control__/link` and the `get_location` MCP tool read
+`sol:dev`, so `GET /__control__/link` and the `get_location` MCP tool read
 where the app is, and `POST /__control__/link` or `open_link` opens a
-screen directly. `srt render --link /settings` renders that screen. A hot
+screen directly. `sol render --link /settings` renders that screen. A hot
 reload starts the rebuilt app at the path it was on: the runtime hands the
 last reported path to the new run as `env.launchLink`.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@solidrt/router",
-  "version": "0.0.65",
+  "version": "0.0.66",
   "license": "MIT",
   "funding": "https://github.com/sponsors/wellawaretech",
   "author": "Antoine van Wel",
@@ -16,6 +16,6 @@
   ],
   "peerDependencies": {
     "@solidjs/signals": "2.0.0-rc.13",
-    "@solidrt/core": "0.0.65"
+    "@solidrt/core": "0.0.66"
   }
 }

package/src/router.tsx

@@ -2,10 +2,10 @@
 // navigation, the back step, blocking, links in and the location out, the
 // JSX tree (`<Route>`) and the components that render the matched routes.
 // Everything here is built on what core offers every app (onBack, onLink,
-// env.launchLink, reportLocation from srt:dev); core knows nothing of routes.
+// env.launchLink, reportLocation from sol:dev); core knows nothing of routes.
 import { createSignal, createMemo, createContext, createEffect, useContext, untrack, onCleanup, children, Show, For } from "@solidrt/core"
 import { env, onBack, onLink } from "@solidrt/core"
-import { reportLocation } from "srt:dev"
+import { reportLocation } from "sol:dev"
 import { createRootRoute, createRoute, formatPath, linkToPath, matchPath, place } from "./route"
 import type { AnyRoute, Match, ParamsOf, RawParams, Route as RouteValue } from "./route"
 import { back as stepBack, changed, currentPath, findTabs, initialState, push, replace, reset, resolve } from "./stack"