devframe 1.2.0 is out (release notes). We're on devframe and @devframes/hub ^1.1.0.
What 1.2.0 brings that matters here:
- vite: the hub shares an https dev server for its WebSocket (devframes/devframe#419), so a Vite hub on https connects without a side-car port
- hub / hub-ui: localized dock, command and launcher titles, a translated hub UI and a language setting
- hub:
defaultChildId is always set, so client docks load reliably
To do
- Bump
devframe and @devframes/hub to ^1.2.0 in packages/ng-devtools/package.json (and the root if listed) and update the lockfile
- Check our own Vite upgrade handling (
packages/ng-devtools/src/vite.ts) still behaves the same next to the upstream https change
- Run
pnpm test:devtools, pnpm test:panel, pnpm typecheck, pnpm test:axe (the hub UI changed) and pnpm extension:build, and check the hub dock rail and panel in a browser
devframe 1.2.0 is out (release notes). We're on
devframeand@devframes/hub^1.1.0.What 1.2.0 brings that matters here:
defaultChildIdis always set, so client docks load reliablyTo do
devframeand@devframes/hubto^1.2.0inpackages/ng-devtools/package.json(and the root if listed) and update the lockfilepackages/ng-devtools/src/vite.ts) still behaves the same next to the upstream https changepnpm test:devtools,pnpm test:panel,pnpm typecheck,pnpm test:axe(the hub UI changed) andpnpm extension:build, and check the hub dock rail and panel in a browser