Skip to content

DEV: Switch to type="module" for translation files #33126

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 9, 2025

Conversation

davidtaylorhq
Copy link
Member

We will be moving towards type="module" for all of Discourse's JS
bundles in the near future. This commit makes a start by applying the
change to translation bundles.

This was previously merged, but the lack of apply_cdn_headers on the locales controller led to CORS errors on sites with CDNs.

We will be moving towards `type="module"` for all of Discourse's JS
bundles in the near future. This commit makes a start by applying the
change to translation bundles.
@davidtaylorhq davidtaylorhq merged commit a2b0c19 into main Jun 9, 2025
16 checks passed
@davidtaylorhq davidtaylorhq deleted the type-module-translations branch June 9, 2025 12:13
martin-brennan pushed a commit that referenced this pull request Jun 10, 2025
We will be moving towards `type="module"` for all of Discourse's JS
bundles in the near future. This commit makes a start by applying the
change to translation bundles.

This was previously merged, but the lack of `apply_cdn_headers` on the
locales controller led to CORS errors on sites with CDNs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants