fix: interpret mjs as text/javascript#1612
Merged
Merged
Conversation
yoganandaness
approved these changes
Jul 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The latest PDFjs package uses moduler js extension .mjs. This PR introduces a fix to interpret .mjs files as text/javascript in our Nginx configuration when the docker image is built.
Motivation and Context
The change is required to prevent .mjs files (ES module workers like pdf.worker.min.mjs) from being served as application/octet-stream which was causing them to be rejected by the browser's strict module MIME check.
Changes
How Has This Been Tested?
Fixes Jira Issue
https://jira.ess.eu//browse/SWAP-5650
Depends On
Tests included/Docs Updated?