Add blog post: web-performance-in-2026-a-practical-guide.mdx#145
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughA new MDX blog post file is added at ChangesNew Web Performance Blog Post
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
content/blog-post-2026-06-23/web-performance-in-2026-a-practical-guide.mdxParsing error: Invalid left-hand side in prefix operation. (1:2) Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
codeant-ai
Bot
added
the
size:M
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@content/blog-post-2026-06-23/web-performance-in-2026-a-practical-guide.mdx`:
- Line 7: The `image` field in the frontmatter references a file path that does
not exist, which will cause the Velite `s.image()` validator to fail at build
time. Either add the missing image file at the referenced path or remove the
`image` field from the frontmatter entirely. If you choose to keep the image
reference, ensure the image file is placed in the correct directory structure
relative to the blog post file.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: a1cb288a-1073-4ca3-addd-4301555f6c36
📒 Files selected for processing (1)
content/blog-post-2026-06-23/web-performance-in-2026-a-practical-guide.mdx
| date: '2026-06-23' | ||
| tags: ['Web performance', 'Frontend', '2026'] | ||
| published: true | ||
| image: './images/post-image.png' |
There was a problem hiding this comment.
🎯 Functional Correctness | 🔴 Critical
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify that the image file exists at the expected path.
# Expected location based on frontmatter
find . -name "post-image.png" -type f
ls -la "content/blog-post-2026-06-23/images/post-image.png" 2>/dev/null && echo "✓ Image file exists" || echo "✗ Image file NOT found"Repository: deepu0/frontend-junction
Length of output: 185
🏁 Script executed:
#!/bin/bash
# Check directory structure and look for any image files in the blog post directory
echo "=== Directory structure of blog-post-2026-06-23 ==="
ls -la "content/blog-post-2026-06-23/" 2>/dev/null || echo "Directory not found"
echo ""
echo "=== Looking for image files in the blog post area ==="
find "content/blog-post-2026-06-23" -type f \( -name "*.png" -o -name "*.jpg" -o -name "*.jpeg" -o -name "*.webp" -o -name "*.gif" \) 2>/dev/null || echo "No image files found"
echo ""
echo "=== Checking if images subdirectory exists ==="
test -d "content/blog-post-2026-06-23/images" && echo "Images directory exists" || echo "Images directory does NOT exist"Repository: deepu0/frontend-junction
Length of output: 555
Add the missing image file or remove the image reference from frontmatter.
The frontmatter references ./images/post-image.png (line 7), but the image file and the images/ directory do not exist. Velite's s.image() validator will fail at build time, preventing the post from being published. Either add the image file at content/blog-post-2026-06-23/images/post-image.png or remove the image field from frontmatter.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@content/blog-post-2026-06-23/web-performance-in-2026-a-practical-guide.mdx`
at line 7, The `image` field in the frontmatter references a file path that does
not exist, which will cause the Velite `s.image()` validator to fail at build
time. Either add the missing image file at the referenced path or remove the
`image` field from the frontmatter entirely. If you choose to keep the image
reference, ensure the image file is placed in the correct directory structure
relative to the blog post file.
![codeant-ai[bot]](https://avatars.githubusercontent.com/in/646884?s=60&v=4){kind=small}
| --- | ||
| title: 'Web performance in 2026: A Practical Guide' | ||
| description: 'A comprehensive guide to web performance for modern frontend development in 2026.' | ||
| date: '2026-06-23' | ||
| tags: ['Web performance', 'Frontend', '2026'] | ||
| published: true | ||
| image: './images/post-image.png' |
There was a problem hiding this comment.
Suggestion: This post is added under content/blog-post-2026-06-23/, but the Velite collection only ingests blog/**/*.mdx from content. As a result, this new article will never be included in #site/content, so it will not appear on blog pages, tags, sitemap, or static params. Move the file under content/blog/ (or expand the collection pattern) so it is actually published. [incomplete implementation]
Severity Level: Critical 🚨
- ❌ Blog listing page /blog never shows this article.
- ❌ Individual post route for this article never generated.
- ⚠️ Tags and sitemap exclude this article's metadata.Steps of Reproduction ✅
1. Open `velite.config.ts` and observe the posts collection definition at lines 11–15:
`pattern: 'blog/**/*.mdx'` with `root: 'content'` at line 31, meaning only files under
`content/blog/**/*.mdx` are ingested into `#site/content`.
2. Note that this PR adds the new MDX file at
`content/blog-post-2026-06-23/web-performance-in-2026-a-practical-guide.mdx` with
frontmatter on lines 1–7; this path `blog-post-2026-06-23/...` does not match the
configured `blog/**/*.mdx` pattern, so Velite will never load it.
3. Start the Next.js app (which consumes Velite output via `#site/content` mapped in
`tsconfig.json:23`) and navigate to `/blog`; the listing page at `app/blog/page.tsx:1–6,
29–35` imports `posts` from `#site/content` and renders only those entries, so the "Web
performance in 2026" article never appears.
4. Check other consumers of `posts` such as the post detail route
`app/blog/[...slug]/page.tsx:1–3, 71–72`, tags pages `app/tags/page.tsx:3, 16–18` and
`app/tags/[tag]/page.tsx:1–5, 25–27`, the homepage latest posts `app/page.tsx:4, 72–85`,
and the sitemap `app/sitemap.ts:3, 38–45`; all source their data from `posts`, so this
article is missing from all blog routes, tag listings, homepage highlights, and sitemap
entries.
(Use Cmd/Ctrl + Click for best experience)
Prompt for AI Agent 🤖
This is a comment left during a code review.
**Path:** content/blog-post-2026-06-23/web-performance-in-2026-a-practical-guide.mdx
**Line:** 1:7
**Comment:**
*Incomplete Implementation: This post is added under `content/blog-post-2026-06-23/`, but the Velite collection only ingests `blog/**/*.mdx` from `content`. As a result, this new article will never be included in `#site/content`, so it will not appear on blog pages, tags, sitemap, or static params. Move the file under `content/blog/` (or expand the collection pattern) so it is actually published.
Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix1 participant
User description
Blog post about Web performance for Frontend Junction
CodeAnt-AI Description
Publish a new guide on web performance for 2026
What Changed
Impact
✅ New published blog content✅ Easier access to web performance guidance✅ Clearer frontend performance advice💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.
Summary by CodeRabbit
Documentation