⚡ Fix favicon: use static PNG instead of broken dynamic SVG #59
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.


Problem
The
icon.tsxwas recreating the logo SVG inline withtransformattributes that don't render correctly at small sizes in Chrome tabs.Solution
Replace with a static
icon.pnginsrc/app/which Next.js will automatically use as the favicon.Before/After
Before: Broken/clipped favicon in Chrome tabs
After: Clean PNG favicon that renders correctly at all sizes
Note
Low Risk
Simple asset/UI change that removes an edge-rendered icon generator; main risk is missing/incorrect
icon.pngplacement causing a broken favicon/logo.Overview
Stops generating the app icon via
src/app/icon.tsx(NextImageResponseSVG) and instead relies on a staticicon.pngasset for more reliable favicon rendering.Updates
DashboardHeaderto display the new PNG logo next to the title and tweaks the title typography (weight/tracking).Written by Cursor Bugbot for commit 94bacb3. This will update automatically on new commits. Configure here.