-
-
Notifications
You must be signed in to change notification settings - Fork 110
Log typescript errors on build dictionaries #167
Copy link
Copy link
Open
Labels
bugSomething isn't workingSomething isn't workingbundlingRelated to the way intlayer is bundled on application (Next.js, Vite.js, Nuxt.js, etc)Related to the way intlayer is bundled on application (Next.js, Vite.js, Nuxt.js, etc)featureA request, idea, or new functionalityA request, idea, or new functionalityrefactorRefactor a part of the codebaseRefactor a part of the codebase
Description
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingbundlingRelated to the way intlayer is bundled on application (Next.js, Vite.js, Nuxt.js, etc)Related to the way intlayer is bundled on application (Next.js, Vite.js, Nuxt.js, etc)featureA request, idea, or new functionalityA request, idea, or new functionalityrefactorRefactor a part of the codebaseRefactor a part of the codebase
A PR (110) was started to improve visibility of missing translations by logging TypeScript errors (e.g. unresolved keys in
t()functions) during the build.However, this change introduced undocumented side effects that must be resolved.
Tasks
pnpm intlayer buildto reproduce and trace the issue..js,.ts,.jsx,.tsx, or.jsoncontent declaration files) are correctly logged during the build.dictionariesbuild works as expected, including for all supported content file formats docs.