Repair HTMX symlink in Docker builds - #6
Open
jhunterjActual wants to merge 1 commit into
Open
Conversation
jochengcd
reviewed
Aug 1, 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
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.
Summary
static/js/htmx.min.jsis a Git symbolic link to the versioned HTMX asset. On Windows checkouts where Git symlink support is disabled, it is materialized as a regular text file containing only the target filename.Docker previously copied that text file into the Linux image. Browsers then attempted to execute
htmx_2_0_8.min.jsas a JavaScript identifier and reported:Recreate the symbolic link inside the Linux image after copying the Django source. This produces the expected result regardless of how the Windows host checked out the Git symlink.
Testing
htmx.min.jsis a symbolic link tohtmx_2_0_8.min.js.var htmx=function(){.git diff --checkpass.