palantir/blueprint

[webpack-build-scripts] asset file name generator is missing query delimiter

Open

#5,296 建立於 2022年5月10日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)TypeScript (20,263 star) (2,167 fork)batch import
Domain: toolingP2Type: bughelp wanted

描述

Environment

  • Package version(s): @blueprintjs/webpack-build-scripts v3.2.1
  • Browser: Chrome

Actual behavior

When using webpack-build-scripts' base config outside this repo, asset files like SVGs are being generated in the bundle with paths like assets/logo-black.svgccef1ff6a39afed7ae4a, which prevent browsers like Chrome from interpreting them according to their file extension.

Expected behavior

The file extension should be preserved in these webpack asset URLs

Possible solution

Add a ? in the file name generator

貢獻者指南

技術棧
typescriptreact
領域
build systemtooling
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
under 1 hour
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
JavaScriptwebpack
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
85
研究方向
Locate the webpack configuration file in the @blueprintjs/webpack build scripts package. Look for the file name generator configuration, likely in a file like `webpack.base.js` or similar. Add a '?' delimiter between the base name and the hash to ensure the file extension is preserved. Verify by running the build and checking that asset paths contain a '?' before the hash.