continue hallucinated [email protected] and i waited on a 404 for 11 min
tried to wire openapi from our zod schemas last night. continue's apply edit added import { createDocument } from "zod-openapi" and pinned [email protected] in package.json.
npm install just… sat there. no error for ages. then a wall of 404s. package doesn't exist — closest thing is zod-to-openapi and even that wants a different import shape.
my $20/mo continue tab is fine. the silent wrong dep is not.



5 comments
Join the discussion
Log in to comment.
did you catch it from the lockfile diff or only after ci? cursor did something similar to me last week with
@hookform/resolvers/zod/v4— install somehow succeeded and thentscexploded with "Cannot find module".curious if continue at least warned in the chat or just applied the edit quiet.
i paste
npm view <pkg> versioninto the chat before accept now. annoying ritual, but cheaper than 11 min of spinner faith.if the client can invent registry names with no resolve check, it's basically a confident typo generator.
yeah. agents keep inventing the hyphenation —
zod-openapi,zod-openapi-kit, whatever sounds package-y. sticky on my desk is justzod-to-openapi/@asteasolutions/zod-to-openapibecause i burned a whole afternoon on a phantom pin once.npm view before accept is cheaper than 11 min of spinner faith. my $20/mo tab can stay; the silent wrong dep cannot.
I demo'd Continue live last month and it invented
@hookform/resolvers-zod. Install hung, audience watched the spinner, I screenshotted the red terminal for the slide deck.npm viewbefore accept is now the first bullet on my "don't trust apply" card. Still burns me that the chat stayed cheerful the whole time.continue did the same to me with
[email protected]— except that one does exist, just not the export path it invented.pnpm addfinished in 4s. then vitest died oncreateClient is not a function. i only noticed because the lockfile diff looked… too clean.do you pin known-good packages in AGENTS.md or just eyeball every apply?