medusajs/medusa · warning

Skipped ${skippedIcons.length} icons. Check the logs for mor

Error message

Skipped ${skippedIcons.length} icons. Check the logs for more information.

What it means

After the icons command finishes fetching and transforming SVGs, it reports how many icons were added to the skippedIcons list (from missing URL or failed fetch). This is a summary warning only — the command continues and generates the index file without the skipped icons.

Source

Thrown at packages/design-system/toolbox/src/commands/icons/command.ts:161

      
            const svgElement = screen.getByTestId("icon")

            expect(svgElement).toBeInTheDocument()

            cleanup()
          })
        })
      `

      await fse.outputFile(testFilePath, testFile)
    })

    await Promise.all(requests)
  }
  logger.success("Successfully transformed SVGs")

  if (skippedIcons.length) {
    logger.warn(
      `Skipped ${skippedIcons.length} icons. Check the logs for more information.`
    )
  }

  logger.info("Generating index file")

  await generateIndex(output)

  logger.success("Successfully generated index file")

  logger.success(`Successfully generated ${length} icons ✨`)
}

View on GitHub (pinned to 5e06e544a2)

Solutions

1. Cross-reference earlier 'Failed to fetch icon ...' warnings to see exactly which icons skipped
2. Fix the affected Figma nodes (or the images map) and re-run to get a complete icon set
3. Verify the generated index/components omit the skipped icons intentionally before publishing

if (skippedIcons.length) {
  // fail the CI build or report the missing icons explicitly
  throw new Error(`Icons skipped: ${skippedIcons.join(", ")}`)
}

When it happens

Trigger: One or more icons hit the missing-URL or failed-fetch paths during generateIcons; the count is reported at the end.

Common situations: Bulk generation with a few broken/moved Figma nodes or a brief network blip; expected noise when the Figma file is mid-refactor.

Related errors

• Failed to fetch icon ${icon.name}. Skipping...
• Unsupported gradient type: ${values.type}
• The gradient type "${gradient.type}" is not supported.

AI-assisted analysis of medusajs/medusa@5e06e544a2 (2026-08-27). Data as JSON: /api/errors/c752250d5c0ddd5d. Report an issue: GitHub.