LinkSwift / Nhật ký kiểm chứng cho bài viết ts4m.dev
Repo: https://github.com/Pranav-Saraswat/LinkSwift
Commit: b57c8d6e49c201f2e80148c0d0d01ba0a8c0176a
Thời điểm: 2026-10-15T07:35:03+00:00
Môi trường: Node 22.14.0, Linux x64

Kết quả từng bước (bản nguồn không chỉnh sửa):

PASS · npm ci --ignore-scripts --no-audit --no-fund
489 dependencies installed from the committed lockfile. Dependency lifecycle scripts disabled.

PASS · npm run prisma:generate --workspace=@url-shortener/database
Prisma Client5.22.0 generated with DATABASE_URL unset. No database connection required.

PASS · npm test -- --maxWorkers=1 --minWorkers=1
Existing URL validation, bot heuristic, and routing unit tests. Single worker bounds resource use.

PASS · npm run build --workspace=@url-shortener/api
TypeScript compile only; does not establish runnable production packaging.

PASS · npm run build --workspace=@url-shortener/web
Vite6.4.3 production bundle. Main JS791.99kB, gzip232.52kB; chunk-size warning. Vite does not run TypeScript type checking.

PASS · npm run dev --workspace=@url-shortener/web -- --host 127.0.0.1 --port 5178 --strictPort
Temporary loopback-only preview. GET /, /src/main.tsx, /src/App.tsx, /src/components/api.ts returned HTTP200. No API requests made. Owned process stopped and port5178 confirmed closed. Article command omits verification port override and uses Vite default5173 when free.

FAIL · npm run build
Turbo2.10.4 cannot resolve workspace: missing packageManager/devEngines.packageManager field. Source turbo.json also retains pipeline instead of tasks.

FAIL · npx tsc -p apps/web/tsconfig.json --noEmit
Implicit any and empty-array state typing errors in UrlShortener.tsx and UrlStatistics.tsx.

FAIL · NODE_ENV=test DATABASE_URL=postgresql://unused:unused@127.0.0.1:15432/linkswift_validation node apps/api/dist/index.js
Import fails before startup with ERR_UNKNOWN_FILE_EXTENSION for packages/database/index.ts. No server or worker starts.

Giới hạn kiểm chứng:
- No Docker containers, database, Redis service, API listening server, Kubernetes deployment, or Terraform/cloud resources were started or modified.
- No real credentials or production data used. No claim of working end-to-end link creation, redirect, analytics, authentication, or deployment.
- Existing unit tests and successful individual builds do not establish production readiness, security completeness, concurrency guarantees, or multi-cloud operation.
- Source-level concerns (shared blocking Redis connection, stale click count cache, non-atomic single-use links) were not runtime-tested with external services.
- Only the original repository source was tested; no fixes were applied to make checks pass.