apps/web · scn-chat · Tangled

ATProto-based AI Assistant Chat interface.

scn-chat apps web

2 folders · 4 files

at admin-config-export

· A reply's step dots stay under the sticky header and composer as the chat scrolls beneath them. The rail is now its own stacking context, so the z-index that lifts each dot over its segment no longer ranks it against the whole page. · 1w ago

A reply's step dots stay under the sticky header and composer as the chat scrolls beneath them. The rail is now its own stacking context, so the z-index that lifts each dot over its segment no longer ranks it against the whole page.

Settings and admin forms keep Save disabled until the form differs from what was saved, and say "Unsaved changes" beside it until then. SaveBar reads this from its form's context, and a form that adds, such as Issue key or Add plugin, passes adds so it never says so. Leaving a page doesn't ask. Preferences now starts over from the stored record after a save, as the other forms do.

The app has one version, the root package.json's, now 0.1.1 to match the latest release, and CHANGELOG.md records what each release changed, with what has landed since 0.1.1 under Unreleased. The workspace packages under apps/ and packages/ drop the 0.1.0 they never kept up, while plugins keep their own versions, which the admin's plugin list shows. pnpm release <version> cuts a release: it dates Unreleased, bumps the version, commits, makes an annotated tag, pushes, and publishes the GitHub Release with that version's section as its notes, refusing unless main is clean and current and Unreleased holds something. docs/releasing.md has the versioning rules and the steps, and CLAUDE.md says to add a changelog line with each change someone would notice.

Rebuild the web app on TanStack Start and Router, with routes at /chat and /shared.

Shiki's Oniguruma engine, a 600 KB wasm, is no longer built. Shiki's full bundle names it for its shorthand highlighter, which the app never uses, since @streamdown/code highlights with Shiki's JavaScript engine, so the wasm was built and precompressed on every build but never loaded. vite.config.ts aliases shiki/wasm to a stand-in, parts/no-wasm.ts, that fails to load with a message saying why, so anything that did reach for the engine would say so rather than highlight nothing. Code built through the alias still highlights in Chrome. The web UI spec says so beside the rehype-raw stand-in.

vitest.config.ts

Compile the web app with React Compiler, through plugin-react's Babel preset, in the browser build and in tests. Server rendering stays uncompiled, since it renders once.