Requested custom icon is returning randomly in production site
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- nuxt, typescript
- Domain
- frontend
Research direction
Start by reproducing the production-only failure with @nuxt/icon 1.9.1, @nuxt/ui 2.18.4, and Nuxt 3.13.0, focusing on requests for the custom m-icon:times icon and the reported error. Done means the requested custom icon loads consistently in the production site instead of returning other icons.
Written by the indexing model from the issue text.
Description
This bug is so random and it's only happen on our production site. Sometimes it happen, sometimes not. I tried create a reproduction but it's only happen on our production site.
But you can see from the screenshot below that the request to times icon is returning 2 other icons. It return the error message: [Icon] failed to load icon m-icon:times
Versions:
"@nuxt/icon": "1.9.1",
"@nuxt/ui": "2.18.4",
"nuxt": "3.13.0"
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 97
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nuxt/icon
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Allow separate providers for SSR and client (`provider: { server, client }`)Possibly taken @pont1s claimed this 24 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
Remote server bundle duplicates concurrent collection downloadsPossibly taken @onmax claimed this 47 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
Similar issues
-
agent/scanner help wanted hive/claimed-by-scanner kind/bug stage/020-claimed
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
hivecommons/rationguard#315 ·
Maintainers usually reply within 1 day
-
agent-ready area: ui-sdk priority: p3 type: chore
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
schlessera/brain-kit#2534 ·
Maintainers usually reply within 1 day
-
bug lane:gh-5
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
LLM-4-People/bridlewise-testing#122 ·
Maintainers usually reply within 1 day
-
bug priority: P2
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
enhancement priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day