fix(devkit): add font file extensions to binaryExts in generate-files.ts #6439
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.
Add font file extensions to the list of extensions that should not be rendered with ejs
Current Behavior
When using generateFiles, font files (.woff2, .ttf, etc.) are treated as template files and are rendered by ejs. However, they are binary files and they sometimes contain characters that interfere with ejs's templating engine, resulting in errors like this:
Custom generators can conceivably contain font files in order to generate a web app so it's safer to make sure ejs does not try to render them.
Expected Behavior
Font files should be in the binaryExts list in order to be excluded from ejs rendering, just like image files.
Related Issue(s)
Fixes #5213