Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[BUG] 500 Maximum call stack size exceeded. Customize this page

Open
#436 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
nuxtjs, typescript
Domain
frontend

Research direction

Start by reproducing the error with the provided Nuxt v4.1.3, @nuxt/icon v2.0.0, and Vue 3.5.22 setup. Inspect nuxt.config.ts and the @nuxt/icon module path while rendering . Done means the example icon renders without the 500 Maximum call stack size exceeded error.

Written by the indexing model from the issue text.

Description

When using the component with @nuxt/icon v2.0.0 and Nuxt v4.1.3, the application throws a “Maximum call stack size exceeded” error.
This happens as soon as I render any icon in a component.
Example:
<template> <Icon name="uil:github" style="color: black" /> </template> Error Output 500 Maximum call stack size exceeded.
Environment:
{ "name": "nuxt-callkit", "type": "module", "private": true, "dependencies": { "@nuxt/icon": "2.0.0", "nuxt": "4.1.3", "vue": "3.5.22", "vue-router": "4.5.1" } }
nuxt.config.ts:
// https://nuxt.com/docs/api/configuration/nuxt-config export default defineNuxtConfig({ compatibilityDate: '2025-07-15', devtools: { enabled: true }, css: ['~/assets/css/main.css'], modules: ['@nuxt/icon'], })
What I Tried
I suspected the issue might be caused by a subdependency conflict.
After removing the ^ from the version numbers in my package.json, the project built correctly, but the runtime error persisted.

Dominant language
TypeScript
Stars
1.2k
Forks
97
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nuxt/icon

All issues in nuxt/icon

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.