chore(web): migrate the UI to SvelteKit 3 and drop the two audit exceptions
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, typescript
Research direction
Start with the errors listed in the issue: run pnpm run build and svelte-check in web/, then open web/src/lib/browse-nav.ts (the goto() call near line 140) and the page.url reads in web/src/routes/+layout.svelte and web/src/routes/browse/+page.svelte. The bits-ui peer on kit 3 is an upstream blocker, so check that before editing. Done means task web:test, task web:build and task web:drift pass on kit 3, and audit.ignore and the cookie override are gone from web/pnpm-workspace.yaml.
Written by the indexing model from the issue text.
Description
Problem
Two low-severity @sveltejs/kit advisories are fixed only in kit 3:
- GHSA-pfhg-q3qv-9q6r: URL redirection to an untrusted site through an enhanced form submission.
- GHSA-27mw-82g8-phjj: XSS through an untrusted cache-control header in a prerendered page.
Neither is reachable in this UI. web/src/routes/+layout.ts sets ssr = false and prerender = false, the UI has no use:enhance, no form actions, no setHeaders and no server files. #183 therefore lists both under audit.ignore in web/pnpm-workspace.yaml, so task web:audit passes. That exception should go when the UI moves to kit 3.
What the migration needs
A trial upgrade (kit 3.1.0, adapter-static 4.0.0, svelte 5.57.2) found:
pnpm run buildfails with sixmodule_removed_liberrors: kit 3 removed modules the UI imports.svelte-checkreports eight errors:page.urland itssearchParamsare now read-only (ReadonlyURLSearchParams) atsrc/routes/+layout.svelte:21,69,src/routes/browse/+page.svelte:38,215,219,228andsrc/routes/workbench/+page.svelte:50;goto()no longer acceptsnoScroll(src/lib/browse-nav.ts:140).
- vitest exits 1 although all 48 tests pass, so something in the test setup breaks under kit 3.
[email protected], pulled in by[email protected], declares an optional peer on kit^2.21.0. runed 0.38 supports kit 3, but bits-ui has not moved to it yet.
Done when
- The UI builds and passes
task web:test,svelte-check,task web:build,task web:driftand the UI gates on kit 3. audit.ignoreinweb/pnpm-workspace.yamlis empty or gone.- The
cookie@<0.7.0override inweb/pnpm-workspace.yamlis dropped: kit 3 depends oncookie ^2.
🤖 Generated with Claude Code
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- Avg merge
- 5h 16m
- Merged PRs (30d)
- 107
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from seanb4t/codegraph-go
-
area:indexer bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
seanb4t/codegraph-go#385 ·
Maintainers usually reply within 1 day
-
chore needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
seanb4t/codegraph-go#380 ·
Maintainers usually reply within 1 day
-
chore needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
seanb4t/codegraph-go#379 ·
Maintainers usually reply within 1 day
-
chore needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
seanb4t/codegraph-go#362 ·
Maintainers usually reply within 1 day
-
area:query bug priority:low spec-needed
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
seanb4t/codegraph-go#355 ·
Maintainers usually reply within 1 day
All issues in seanb4t/codegraph-go
Similar issues
-
enhancement exporter/awskinesis needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
open-telemetry/opentelemetry-collector-contrib#53334 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
erigontech/erigon#26523 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
SocialGouv/iterion#3376 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
seaweedfs/seaweedfs#12740 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day