Repository navigation
Terminal-style overview dashboard + unbreak Vercel deploys - #16
Merged
Merged
Conversation
Rework the overview page from generic metric cards into a dense, terminal-styled risk console: - Context strip (snapshot, as-of, regime, stress, counts) with a live/loading status indicator. - Compact metric row replacing the executive Metric cards. - Risk path chart upgraded from LineChart to ComposedChart with a gradient area, grid, and policy reference lines at the 15% review and 30% elevated impairment thresholds (mirroring src/atlas/domain/reports/builder.py). - New "Exposure by portfolio" pane ranking portfolios by mean P(impairment). - Tone helpers (risk/stress/regime/severity) centralised in the page. The tooltip formatter takes recharts 3's ValueType (possibly undefined) rather than a bare number. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
PR #9 bumped vite 6 -> 8 (rollup 4). The object form of build.rollupOptions.output.manualChunks now resolves against ManualChunksFunction and fails to typecheck: vite.config.ts(25,11): error TS2769: No overload matches this call. 'charts' does not exist in type 'ManualChunksFunction' Since the build script is `tsc -b && vite build`, this broke every deployment on master independently of any feature work. Switched to the function form; the emitted chunks (charts, tables, react-vendor) are unchanged. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The project's install command was overridden to `npm install`, which
ignores frontend/pnpm-lock.yaml and re-resolves the tree from the
registry. A dependency in that fresh tree now ships a `workspace:*`
spec, which npm cannot parse:
npm error code EUNSUPPORTEDPROTOCOL
npm error Unsupported URL Type "workspace:": workspace:*
Every deployment since ebea833 failed this way, including the #14
production build, so the live site was pinned to a stale commit.
vercel.json build settings take precedence over dashboard project
settings, so pinning the install command here fixes it in-repo and
keeps it under review. --frozen-lockfile also makes the deployed tree
match the committed lockfile, which the npm path never did.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
PR #9 bumped typescript 5.9.3 -> 7.0.2. TypeScript 7 is the native port and changes the compiler API surface. Vercel's @vercel/node builder compiles frontend/api/atlas/[...path].ts with the locally installed TypeScript, and crashes on it: Using TypeScript 7.0.2 (local user-provided) Error: Cannot read properties of undefined (reading 'readFile') The vite build itself succeeds and emits identical chunks — the failure is only in the serverless function stage, after the client bundle is already built, which is why it reads as a green build followed by a failed deployment. Pinned with ~ rather than ^ so dependabot cannot walk it back to 7 until Vercel's builder supports it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Reworks the overview page into a dense, terminal-styled risk console, and fixes the two separate reasons no Vercel deployment has succeeded since
ebea833.The deploy breakage
Production (
atlas-os-zimmermann.vercel.app) has been pinned toebea833for ~13 hours. Every deployment since — including the #14 production build — failed. Two independent causes:1. Install command. The project's install command is overridden to
npm install, which ignoresfrontend/pnpm-lock.yamland re-resolves from the registry. Something in that fresh tree now ships aworkspace:*spec:Fixed via
frontend/vercel.json—vercel.jsonbuild settings take precedence over dashboard project settings, so this is fixed in-repo and stays under review.--frozen-lockfilealso makes the deployed tree match the committed lockfile, which the npm path never did.2. Typecheck. PR #9 bumped vite 6 → 8 (rollup 4), which broke the
manualChunksobject form. Since the build script istsc -b && vite build,mastercould not build even with the install fixed. This one is pre-existing and unrelated to the dashboard work — it's isolated in its own commit.Dashboard changes
MetriccardsLineChart→ComposedChartwith gradient area, grid, and policy reference lines at the 15% review / 30% elevated impairment thresholds (mirroringsrc/atlas/domain/reports/builder.py)Verification
Run against master's upgraded dependency set (recharts 3.9.2, zod 4, TypeScript 7, vite 8, vitest 4):
pnpm install --frozen-lockfile— clean, confirming the lockfile is in synctsc -b— cleanVERCEL=1 vite build— succeeds;charts,tables,react-vendorchunks all still emitted, so themanualChunksrewrite is behaviour-preservingvitest run— 11/11 passingThe tooltip formatter was also updated for recharts 3, which types the value as
ValueType | undefinedrather thannumber.Note
Branched off
masterrather thandeploy/render. PR #14 was squash-merged, so a PR from that branch re-proposes ~920 lines of already-merged content and invites phantom conflicts.🤖 Generated with Claude Code