Back to feed
Dev.to
Dev.to
7/20/2026
The original title is "Every icon vanished: a Metro debugging story (featuring a babel package from 2017)"

The original title is "Every icon vanished: a Metro debugging story (featuring a babel package from 2017)"

Original: Every icon vanished: a Metro debugging story (featuring a babel package from 2017)

Short summary

A debugging narrative tracing a Metro bundler crash ('Cannot read properties of undefined reading transformFile') to an ancient @babel/[email protected] from 2017, transitively pulled in by @aws-amplify/graphql-types-generator. The author walks through eliminating false leads, identifying the version conflict via package-lock.json inspection, and fixing it with npm overrides in the root package.json.

  • Metro TypeError with no filename usually indicates a broken Babel toolchain, not application code
  • Root cause was @babel/[email protected] (2017) pulled transitively by @aws-amplify/graphql-types-generator
  • Fix: pin @babel/types and @babel/generator with overrides in root package.json

Generated with AI, which can make mistakes.

Is this a good recommendation for you?

Comments

Failed to load comments. Please try again.

Explore more