Skip to content
31 linesCodeBlameRaw

Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.

Projects live: fixes from walking them end to end1{
2 "extends": "./tsconfig.json",
3 "include": [
4 ".react-router/types/**/*",
5 "app/**/*",
6 "app/**/.server/**/*",
7 "app/**/.client/**/*",
8 "workers/**/*",
9 "worker-configuration.d.ts"
10 ],
11 "exclude": ["app/**/*.test.ts"],
12 "compilerOptions": {
13 "composite": true,
14 "strict": true,
15 "lib": ["DOM", "DOM.Iterable", "ES2022", "ESNext.Disposable"],
16 "types": ["vite/client"],
17 "target": "ES2022",
18 "module": "ES2022",
19 "moduleResolution": "bundler",
20 "jsx": "react-jsx",
21 "rootDirs": [".", "./.react-router/types"],
22 "paths": {
23 "~/*": ["./app/*"]
24 },
25 "esModuleInterop": true,
A doc opens at once: the page carries the document's saved state, so the editor mounts without waiting for its live room, which connects in the background and sends only what changed, with a quiet dot that turns green when it's synced; edits made before then are kept and sent once. The editor's code is preloaded from the page and fetched early when you hover a doc, the app's shared code ships in a few chunks instead of a hundred small ones, socket tickets come with the page instead of a round trip, and the artifacts service answers a page, a sidebar and a room in parallel lookups instead of a dozen in a row, reporting its database round trips in Server-Timing. The artifacts guide says how a doc opens, and CONTRIBUTING's Speed section has the numbers.26 "resolveJsonModule": true,
27 // Browser modules tested under Node (`npm test`) name the files they
28 // import with their extension, as Node needs (components/folios/provider.ts).
29 "allowImportingTsExtensions": true
Projects live: fixes from walking them end to end30 }
31}

This file's history is long; its oldest lines are credited to the oldest commit read.