Adding troubleshooting information about Subresource Integrity digests. #1220
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.
Adding this section to the troubleshooting documentation:
Subresource integrity checks fail
Subresource Integrity digests are added to the build output files. For a particular scenario, these checks may fail when deployed. The files are built using
LF
characters, but if your deployment uses a Git repository for deployment (like Azure web sites) and the Git repository is set up to translateLF
characters intoCR/LF
characters, then the checked out files will be different and the digests will be invalid.To fix this, just add a
.gitattributes
file to your deployment repository that will ensure the build files are not modified when checked out: