Skip to content
⌘K
Explore
Download
Docs
Sign in
Sign up
flagon-io
/
g1t
public
Star
0
Overview
Code
Issues
Pull requests
Workflows
Deployments
Insights
Files
Commits
Branches
Tags
Releases
Compare
f776fea310d6819f2321c309109ccffa995278d0
g1t
/
…
/
apps
/
web
/
workers
syntaqx
The docs page behind an expanded diagram no longer scrolls: while a diagram's dialog is open the page's scrolling is held, and scrolling past either end of the diagram stops at the dialog.
f776fea
yesterday
History
..
app.ts
async-hooks.d.ts
env.d.ts
usercontent.ts
..
app.ts
Developer mode: a page that fails can say why. Under Settings, Account, a Developer mode switch (kept per browser in a g1t_dev cookie, like Appearance) makes the error page show the error itself, its message and stack, the address, the time, whether it came from a page the server drew or a navigation in the browser, the routes it was drawn from, the site's build (its stylesheet's hashed name), the browser and the desktop app's version, with Copy details to paste it all into a report; with it off, the page says where to turn it on. A signed-in request with developer mode on is answered by React Router in its development mode (workers/app.ts, a second handler made the first time it is wanted), so an error on the server comes through in full instead of "Unexpected Server Error"; that mode differs from production only in that and in hooks only Vite's dev server sets, and only ever covers the person's own requests. Checked in a production build: a failing repository page shows "counts failed with status 503" and its stack with developer mode on, and the usual page with it off. The workspaces guide covers it under Developer mode.
yesterday
async-hooks.d.ts
Fast pages, required checks on the branch, self-hosted runners, honest incidents
1w ago
env.d.ts
Merge branch 'ask-g1t'
yesterday
usercontent.ts
Merge branch 'worktree-agent-a5b0d9e2733e9e382'
yesterday
