-
Notifications
You must be signed in to change notification settings - Fork 7
Quickstart Next Steps - visit framework pages #715
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Style Review
Found 1 style suggestion(s).
Powered by Vale + Claude
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| /// <reference types="next" /> | ||
| /// <reference types="next/image-types/global" /> | ||
| import "./.next/types/routes.d.ts"; | ||
| import "./.next/dev/types/routes.d.ts"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Auto-generated file accidentally modified with dev path
Medium Severity
The next-env.d.ts file contains a comment stating it "should not be edited," yet the import path was changed from .next/types/routes.d.ts to .next/dev/types/routes.d.ts. The dev in the path suggests this was auto-generated when running next dev and accidentally committed. This may cause TypeScript errors in CI/CD or production builds if those environments generate type files in .next/types/ rather than .next/dev/types/.
vfanelle
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added pretty agent framework buttons at the end of the Calling tools in your agent with Arcade QuickStart


Note
Low Risk
Low risk: mostly documentation/UI refactoring plus a small TypeScript env type import path tweak; main risk is incorrect guide links or mislabeled card types.
Overview
Introduces a reusable
AgentFrameworkTabscomponent that renders the language tabs and framework/MCP client cards, replacing the inline tabs markup inget-started/agent-frameworks.Updates the "Calling tools in your agent" quickstart to show these framework links in Next Steps (and renames the section to Full Example Code), making it easier to jump from the quickstart to framework-specific guides.
Adjusts
next-env.d.tsto reference./.next/dev/types/routes.d.tsinstead of the previous routes types path.Written by Cursor Bugbot for commit 5a1dcd5. This will update automatically on new commits. Configure here.