Skip to content

Conversation

@peer-jslater
Copy link

@peer-jslater peer-jslater commented Oct 15, 2025

Description

When developing on windows multiple problems arose because the theme did not seem to build.
The issue with yarn start was found on https://support.zendesk.com/hc/en-us/requests/13811934.
So that may already be in Zendesk's backlog/workflow somewhere. I've included my implementation of the fix in this PR.
Another issue occurred when I ran i18n:update-translations that's fixed here. See the commit message for details.

I wanted Zendesk to be aware of the problem and my fixes to hopefully save them some time. Here it is.

Screenshots

Checklist

I do not have a mobile device to test on and cannot test on all browsers. So I will not be finishing the checklist.

  • 📗 all commit messages follow the conventional commits standard
  • ⬅️ changes are compatible with RTL direction
  • ♿ Changes to the UI are tested for accessibility and compliant with WCAG 2.1.
  • 📝 changes are tested in Chrome, Firefox, Safari and Edge
  • 📱 changes are responsive and tested in mobile
  • 👍 PR is approved by @zendesk/vikings

@peer-jslater peer-jslater requested a review from a team as a code owner October 15, 2025 15:12
@peer-jslater
Copy link
Author

I cannot mention @zendesk/vikings as recommended here.

This change is needed during `yarn i18n:update-translations`.
Otherwise the translation files are placed in
src/modules/undefined.
During `yarn start`:
Without this change the translations are not correctly identified and
too many bundles are created resulting in error messages:
```
Error: InvalidTemplates - Template(s) with syntax error(s)
Validation error Zendesk.Theme/templates/assets.hbs
Mapping has more items than allowed.
```
@peer-jslater peer-jslater force-pushed the fix-translations-on-windows branch from da0c96e to 6bd68a3 Compare October 15, 2025 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant