Fix 404 errors #2
Open
garlobrian52 wants to merge 21 commits into
Open
Conversation
Co-authored-by: Mohamed <garlobrian52@users.noreply.github.com>
Co-authored-by: Mohamed <garlobrian52@users.noreply.github.com>
Co-authored-by: Mohamed <garlobrian52@users.noreply.github.com>
Scaffold a Next.js example under examples/workflow-email-onboarding that demonstrates durable signup and welcome email workflows using workflow, Resend, and the use workflow/use step directives. Co-authored-by: Mohamed <garlobrian52@users.noreply.github.com>
Update the email onboarding example to match the Workflow DevKit getting-started guide: rename userSignup to handleUserSignup, use a 5s sleep delay, pass the user object to email steps, and rename the follow-up step to sendOnboardingEmail. Co-authored-by: Mohamed <garlobrian52@users.noreply.github.com>
Cursor Cloud Agents were failing with 'Failed to fetch branch/tag ref Blueprint' because no Blueprint branch existed on GitHub. The Blueprint branch has been created separately to track main. Add .cursor/environment.json so agents resolve environment config from the repository and pre-install Go module dependencies on startup. Co-authored-by: Mohamed <garlobrian52@users.noreply.github.com>
Use blueprint/<task>-ee50 for feature branches and Blueprint or main as the base branch. Ambiguous Th_Blueprint-prefixed names without a slash can be misread as ref Blueprint during Cloud Agent startup. Co-authored-by: Mohamed <garlobrian52@users.noreply.github.com>
# Vercel Speed Insights Installation Report
## Summary
Successfully installed and configured Vercel Speed Insights for the Next.js application in the examples/workflow-email-onboarding directory.
## Changes Made
### 1. Package Installation
- **File Modified**: `examples/workflow-email-onboarding/package.json`
- **Change**: Added `@vercel/speed-insights` version ^2.0.0 to dependencies
- **Lock File Updated**: `examples/workflow-email-onboarding/package-lock.json` (801 packages installed)
### 2. SpeedInsights Component Integration
- **File Modified**: `examples/workflow-email-onboarding/src/app/layout.tsx`
- **Changes**:
- Added import: `import { SpeedInsights } from "@vercel/speed-insights/next";`
- Added `<SpeedInsights />` component inside the `<body>` tag after children
- Followed Next.js App Router conventions as specified in the official Vercel documentation
## Implementation Details
The implementation follows the official Vercel Speed Insights quickstart guide for Next.js v13.5+:
- Used the Next.js-specific package import path: `@vercel/speed-insights/next`
- Placed the component in the root layout file for application-wide coverage
- Component is rendered after children as recommended in the documentation
## Verification Steps Completed
✅ **Build Test**: Successfully built the Next.js application with no errors
✅ **Linter Check**: Ran ESLint - no new errors introduced (only pre-existing warnings unrelated to our changes)
✅ **Dependencies**: All dependencies installed correctly via npm
✅ **Lock File**: package-lock.json updated and included in the changes
## Technical Specifications
- **Framework**: Next.js 16.2.7 (App Router)
- **Package Manager**: npm
- **Speed Insights Version**: 2.0.0
- **Package Type**: @vercel/speed-insights/next (Next.js-specific implementation)
## Notes
- The Speed Insights component will automatically track Core Web Vitals and other performance metrics when the application is deployed to Vercel
- No additional configuration is required - the component works out of the box
- The implementation preserves all existing code structure and functionality
- No breaking changes were introduced
## Next Steps
To enable Speed Insights on Vercel:
1. Deploy the application to Vercel
2. Navigate to the Vercel dashboard
3. Select "Speed Insights" from the sidebar
4. Choose the project and click "Enable"
5. After user visits, performance metrics will be visible in the dashboard
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
…vercel-s-vf61fu
Co-authored-by: Mohamed <134189886+garlobrian52@users.noreply.github.com>
Added Vercel configuration file and updated tsconfig.json to exclude docs and examples. Co-authored-by: Mohamed <134189886+garlobrian52@users.noreply.github.com>
Co-authored-by: Mohamed <garlobrian52@users.noreply.github.com>
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
3 participants
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.
Summary
Why
Fixes #
What changed
MCP impact
Prompts tested (tool changes only)
Security / limits
Tool renaming
deprecated_tool_aliases.goNote: if you're renaming tools, you must add the tool aliases. For more information on how to do so, please refer to the official docs.
Lint & tests
./script/lint./script/testDocs