Skip to content

📝 docs(readme): add an "Open in StackBlitz" badge to the README badge rows - #54

Open
vtempest wants to merge 1 commit into
masterfrom
claude/compassionate-noether-fcq290
Open

📝 docs(readme): add an "Open in StackBlitz" badge to the README badge rows#54
vtempest wants to merge 1 commit into
masterfrom
claude/compassionate-noether-fcq290

Conversation

@vtempest

Copy link
Copy Markdown
Collaborator

Adds an Open in StackBlitz badge to every badge row in this repo.

StackBlitz installs from the manifest at the path it is handed, so each badge points at a directory that boots on its own rather than at the repo root:

Badge row Opens
README.md examples/basic-request — the self-contained example the docs already open with <StackBlitzExample>
grab-help-docs/content/docs/index.mdx (the same row, on the docs home) examples/basic-request
packages/quantum-sphere-loading-animation/README.md that package

The badge sits next to the existing "Open in GitHub Codespaces" badge in each row, using StackBlitz's own open_in_stackblitz.svg.

No code, build or docs-pipeline changes — Markdown/MDX only.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Kkb27RSQgLWvRWv1vcdJef


Generated by Claude Code

… rows

Every badge row now carries an "Open in StackBlitz" badge pointing at a
directory that boots on its own — StackBlitz installs from the manifest
at the path it is handed, so each badge targets a package (or a runnable
example) rather than the monorepo root, which would not install.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Kkb27RSQgLWvRWv1vcdJef
@vercel

vercel Bot commented Sep 11, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
grab-url Error Error Sep 11, 2026 3:09pm UTC

@codecov

codecov Bot commented Sep 11, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Copy link
Copy Markdown
Collaborator Author

The test check is red on this PR's head, and it is not this PR's failure — this branch changes three Markdown/MDX files and nothing else.

The same check is red on master. The last six runs of tests.yml on master all failed, starting with the merge of #45; the last green one was #44's merge (run 159). This branch is based on #50's merge, which is already inside that red stretch.

Root cause. packages/grab-url-cli/src/transfer/ytdlp-transfer.ts is missing six symbols that both packages/grab-url-cli/src/index.ts (lines 123-131) and test/page-archive.test.ts (line 32) import from it: findYtDlp, probeYtDlp, runYtDlpDownload, ytDlpInstallHint, parseYtDlpSize, parseYtDlpEta. The module exports buildYtDlpArgs, parseYtDlpProgress and describeYtDlpExit, and the test's vi.mock(..., importOriginal) spread cannot produce the rest — hence [vitest] No "parseYtDlpSize" export is defined on the ... mock on eleven cases. The remaining assertion failures in the same file (buildYtDlpArgs output template, parseYtDlpProgress returning null, the describeYtDlpExit message) are the same drift: the tests describe a version of that module that did not land.

No fix exists to port — the only other open PR, #53, is a publish-provenance change. Fixing this means writing the missing yt-dlp transfer functions, which is well outside a badge-row PR, so I am not widening this one to carry it. Skipping the re-run too: six consecutive red runs on master and a symbol that is absent from the source are not a flake.

master needs that fix on its own; this PR is mergeable as soon as it lands, and nothing here blocks it.


Generated by Claude Code

Copy link
Copy Markdown
Collaborator Author

Second red check on this head, also not this PR's: Vercel (grab-url project) errored.

The bot's own payload still reports "rootDirectory":"docs", which is the failure this repo already has written down in .claude/architecture/documentation.md — "The Vercel deploy is broken, and docs/ is why". The project's Root Directory has pointed at docs since the docs app was renamed docs/grab-help-docs/; turbo resolves no package from there, never writes a .next, and the deploy fails looking for docs/.next/routes-manifest.json. Every deployment of that project is failing, production included.

Quoting that note: "This is a dashboard setting, not a diff — no commit can fix it", and "until that setting changes, a red Vercel check on a PR here says nothing about that PR." The fix is in the Vercel dashboard: Root Directory → grab-help-docs, clear the npm install --prefix=.. Install Command override, leave Build Command unset.

So both red checks on this branch are pre-existing: test (missing ytdlp-transfer exports on master, above) and Vercel (this dashboard setting). Neither is fixable from a Markdown-only PR.


Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant