Pain point · API & developer experience · Blocks work
Undeclared dependencies break Strapi types on strict package layouts
2 source threads · first seen 2026-09
Summary
Published Strapi declaration files reference modules that the packages do not declare, so types can resolve incorrectly or degrade to any with pnpm's global virtual store or Yarn PnP. One downstream repo reported 28 TypeScript errors across its app and plugins.
- Affects
- TypeScript consumers using pnpm or Yarn PnP
- Workaround
- Add packageExtensions entries for the missing dependencies.
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“Every consumer on a strict layout has to rediscover and work around it independently”
“One downstream repo hit 28 hard TypeScript errors across their Strapi app and all four of their plugins from this”