Conversation
Contributor
There was a problem hiding this comment.
🤖 AI Review
Verified both Claude findings against the checked-out code and trusted conventions. Both are confirmed as minor concerns: reduced import-map parse diagnostics and additional serial filesystem I/O during recursive traversal. Codex reported no findings. The traversal claim is narrowed to the verified call counts; a noticeable slowdown was not measured. Validation was static.
Findings
| Severity | Location | Category | Sources | Claim |
|---|---|---|---|---|
| 🟡 MINOR | apps/cli/src/shared/functions/deploy.ts:696 |
error-messages |
claude | Malformed local import maps now produce only Expected a valid JSON string, losing the native parser's syntax detail. The error also lacks file context, making failures harder to diagnose when deno.json references another import map. |
| 🟡 MINOR | apps/cli/src/shared/functions/deploy.ts:969 |
performance |
claude | Recursive traversal adds one serial stat call per directory entry and a readLink call for each directory candidate, increasing filesystem I/O for static-file glob expansion and directory import-map targets. |
Stats
Claude findings: 2 · Codex findings: 0 · Confirmed: 2 · Refuted: 0 · Uncertain: 0
Models: claude-opus-5-5 + gpt-6.1-sol · Trigger: auto · Workflow run
This review runs once per PR. A maintainer can request another with a /ai-review comment.
This branch has not been 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
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.
TL;DR
brings
functions deployunder the effect lintwhats introduced?
deploy.ts,deploy.errors.tsand the new errors unit test join the allow list, and thedeployunit tests follow on the next branchFileSystemandPathservices, shared withfunctions serveandsupabase start, andonWarningis now an effect thatserve.tspassesErrorfailures become an untaggedFunctionDeployErrorand the import map parse error keeps theSyntaxErrorname, so telemetry and traces stay the samedeno.jsonor import map and the list, deploy and function responses decode throughSchema, so a malformed document now readsExpected a valid JSON stringdeployFunctionsbecomesEffect.fnwith the same span name,DEBUGreads throughConfigand dated rate limit headers read the time throughClockDEBUGdriving--verboseref