Remove unused pliny SearchProvider and algolia CSS imports#101
Merged
GordonBeeming merged 3 commits intomainfrom Aug 11, 2025
Merged
Remove unused pliny SearchProvider and algolia CSS imports#101GordonBeeming merged 3 commits intomainfrom
GordonBeeming merged 3 commits intomainfrom
Conversation
Contributor
Author
|
@GordonBeeming 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs. I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review. |
Co-authored-by: GordonBeeming <5680199+GordonBeeming@users.noreply.github.com>
Co-authored-by: GordonBeeming <5680199+GordonBeeming@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Refactor - Remove unused dependencies from the blog
Remove unused pliny SearchProvider and algolia CSS imports
Aug 10, 2025
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR removes unused search provider imports and configurations from the blog codebase. The changes clean up unused pliny SearchProvider infrastructure while preserving the existing custom search functionality.
- Removed unused pliny SearchProvider wrapper and algolia CSS import from the main layout
- Updated search configuration comments to document the actual custom implementation being used
- Added conditional logic to skip unused search.json generation
Reviewed Changes
Copilot reviewed 9 out of 10 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| src/app/layout.tsx | Removed unused SearchProvider wrapper and algolia CSS import |
| data/siteMetadata.js | Updated search config with comments documenting custom implementation |
| contentlayer.config.ts | Added conditional check and logging for search index generation |
| public/*.xml | Generated RSS feed files (not core to the PR purpose) |
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.
After conducting a thorough audit of the blog's dependencies, I discovered that while all npm packages in
package.jsonare actually being used, there were unused imports and provider wrappers that could be removed to clean up the codebase.What was removed:
1. Unused pliny SearchProvider wrapper
SearchProvidercomponent wrapper fromsrc/app/layout.tsximport { SearchProvider, SearchConfig } from 'pliny/search'SearchButton.tsx+ListLayoutGrid.tsx2. Unused algolia.css import
import 'pliny/search/algolia.css'fromsrc/app/layout.tsx3. Updated search configuration
data/siteMetadata.jsto document the actual custom search implementationsearch.jsongeneration incontentlayer.config.tsKey findings:
The original issue mentioned
kbaras an example of unused dependencies, butkbaris actually a transitive dependency through theplinypackage, which is heavily used throughout the codebase for analytics, comments, and content utilities. The real issue was that the plinySearchProviderwas being imported and wrapped around the app but provided no functional value since the blog implements its own custom search.Custom search implementation works via:
/blog?q=...Results:
Visual verification:
The custom search implementation remains fully functional while removing the unused pliny search infrastructure.
Fixes #100.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.