[{"data":1,"prerenderedAt":940},["ShallowReactive",2],{"blog-article-\u002Ftw\u002Fblog\u002Fcargo-cache-vs-target-folder":3},{"id":4,"title":5,"author":6,"body":7,"category":924,"cover":925,"coverAlt":926,"description":927,"draft":928,"extension":929,"meta":930,"navigation":309,"path":931,"publishedAt":932,"seo":933,"stem":934,"tags":935,"translationKey":938,"updatedAt":932,"__hash__":939},"articles_tw\u002Ftw\u002Fblog\u002Fcargo-cache-vs-target-folder.md","Cargo 快取和 target 資料夾有什麼不同？Rust 開發者該刪哪個","Harry",{"type":8,"value":9,"toc":908},"minimark",[10,19,30,36,41,44,61,70,222,233,237,243,246,252,255,258,379,386,407,410,446,449,453,460,478,481,493,496,557,571,574,578,581,595,601,604,669,672,714,721,735,739,742,785,791,795,809,819,822,827,830,834,840,844,850,854,857,860,896,904],[11,12,13,14,18],"p",{},"需要騰出磁碟空間時，通常應該先清理已經不再使用的專案 ",[15,16,17],"code",{},"target"," 資料夾。這裡存放的是個別 Rust workspace 的建置成果，之後重新編譯就能產生。只有在 Cargo 共用快取確實很大、內容損壞，或近期不需要離線開發時，才考慮清理相依套件快取；清掉之後，Cargo 必須重新下載或解壓縮套件。",[11,20,21,22,25,26,29],{},"不要直接刪除整個 ",[15,23,24],{},".cargo"," 資料夾。裡面還可能有 Cargo 設定、registry 認證資料，以及透過 ",[15,27,28],{},"cargo install"," 安裝的命令列工具，這些都不是一般快取。",[31,32,33],"blockquote",{},[11,34,35],{},"本文路徑與指令已於 2026 年 8 月 12 日在 macOS 15.7.7、Cargo 1.84.0、rustc 1.84.0 上驗證。Cargo 可以自訂 Home 與建置資料夾，刪除前請先確認自己電腦上的實際路徑。",[37,38,40],"h2",{"id":39},"先講結論先清-target再考慮-cargo-快取","先講結論：先清 target，再考慮 Cargo 快取",[11,42,43],{},"Cargo 會保存兩種性質不同、但都能重新產生的資料：",[45,46,47,54],"ul",{},[48,49,50,51,53],"li",{},"workspace 裡的 ",[15,52,17],{}," 資料夾，存放該專案的編譯成果；",[48,55,56,57,60],{},"Cargo Home（通常是 ",[15,58,59],{},"~\u002F.cargo","），存放共用下載、解壓縮後的套件原始碼、Git 相依套件、設定、認證資料與已安裝工具。",[11,62,63,64,66,67,69],{},"兩者的復原成本不同。刪除 ",[15,65,17],{}," 主要會增加重新編譯的時間；刪除相依套件快取，除了重新編譯，還可能需要網路。因此對多數開發者來說，舊專案的 ",[15,68,17],{}," 是更合理的第一個清理目標。",[71,72,73,92],"table",{},[74,75,76],"thead",{},[77,78,79,83,86,89],"tr",{},[80,81,82],"th",{},"路徑",[80,84,85],{},"內容",[80,87,88],{},"可以刪除嗎？",[80,90,91],{},"刪除後的影響",[93,94,95,112,128,143,162,181,200],"tbody",{},[77,96,97,103,106,109],{},[98,99,100],"td",{},[15,101,102],{},"project\u002Ftarget",[98,104,105],{},"Debug、Release、增量編譯、文件與不同目標平台的建置成果",[98,107,108],{},"可以，先停止建置",[98,110,111],{},"專案需要重新編譯",[77,113,114,119,122,125],{},[98,115,116],{},[15,117,118],{},"~\u002F.cargo\u002Fregistry\u002Fcache",[98,120,121],{},"已下載的 crate 壓縮檔",[98,123,124],{},"通常可以，但要確定能連網",[98,126,127],{},"Cargo 會重新下載缺少的 crate",[77,129,130,135,138,140],{},[98,131,132],{},[15,133,134],{},"~\u002F.cargo\u002Fregistry\u002Fsrc",[98,136,137],{},"從 registry 解壓縮出的套件原始碼",[98,139,124],{},[98,141,142],{},"Cargo 會重新解壓縮或下載",[77,144,145,154,157,159],{},[98,146,147,150,151],{},[15,148,149],{},"~\u002F.cargo\u002Fgit\u002Fdb"," 與 ",[15,152,153],{},"git\u002Fcheckouts",[98,155,156],{},"Git 相依套件的 repository 與 checkout",[98,158,124],{},[98,160,161],{},"Cargo 會重新抓取與 checkout",[77,163,164,169,175,178],{},[98,165,166],{},[15,167,168],{},"~\u002F.cargo\u002Fbin",[98,170,171,172,174],{},"透過 ",[15,173,28],{}," 安裝的工具",[98,176,177],{},"不可當成快取刪除",[98,179,180],{},"已安裝的指令會消失",[77,182,183,191,194,197],{},[98,184,185,150,188],{},[15,186,187],{},"config.toml",[15,189,190],{},"credentials.toml",[98,192,193],{},"Cargo 設定與 registry 認證資料",[98,195,196],{},"不可以",[98,198,199],{},"建置、registry、Proxy 或登入可能失效",[77,201,202,214,217,219],{},[98,203,204,207,208,207,211],{},[15,205,206],{},"Cargo.toml","、",[15,209,210],{},"Cargo.lock",[15,212,213],{},"src",[98,215,216],{},"專案定義、相依版本鎖定與原始碼",[98,218,196],{},[98,220,221],{},"會直接破壞專案",[11,223,224,225,228,229,232],{},"Windows 的預設 Cargo Home 通常位於 ",[15,226,227],{},"%USERPROFILE%\\.cargo","。如果有設定 ",[15,230,231],{},"CARGO_HOME","，不論使用哪個作業系統，都應以該環境變數指向的位置為準。",[37,234,236],{"id":235},"target-資料夾為什麼會變得這麼大","target 資料夾為什麼會變得這麼大？",[11,238,239,240,242],{},"Cargo 預設把建置輸出寫進 workspace 的 ",[15,241,17],{}," 資料夾。Debug 與 Release profile 使用不同的子資料夾；加入其他編譯目標後，各個 target triple 也會保存自己的成果。增量編譯還會保留中間資料，讓後續建置更快。",[11,244,245],{},"如果同一個 workspace 會建置桌面程式、WebAssembly、多種架構或多組 feature，累積容量遠大於原始碼並不意外。Cargo 官方把這些內容視為可重新產生的建置資料，但刪除仍有代價：下一次建置會從沒有快取的狀態開始。",[11,247,248,249,251],{},"撰寫本文時，MangoDisk repository 的 ",[15,250,17],{}," 佔了 27 GB。同一台 Mac 的 Cargo registry 壓縮檔快取為 189 MB、解壓縮後的原始碼為 1.9 GB，Cargo Git 資料庫則是 17 MB。這只是這台電腦的實測結果，不代表每個人都能釋放相同空間；重點是應該先量測，而不是預設全域快取一定最大。",[37,253,254],{"id":254},"清理前先確認實際路徑與容量",[11,256,257],{},"在 macOS 或 Linux 的 Rust workspace 中，可以先執行這些唯讀指令：",[259,260,265],"pre",{"className":261,"code":262,"language":263,"meta":264,"style":264},"language-bash shiki shiki-themes github-light github-dark","cargo_home=\"${CARGO_HOME:-$HOME\u002F.cargo}\"\n\ndu -sh target 2>\u002Fdev\u002Fnull\ndu -sh \"$cargo_home\u002Fregistry\u002Fcache\" \"$cargo_home\u002Fregistry\u002Fsrc\" \\\n  \"$cargo_home\u002Fgit\u002Fdb\" \"$cargo_home\u002Fgit\u002Fcheckouts\" 2>\u002Fdev\u002Fnull\n","bash","",[15,266,267,304,311,331,357],{"__ignoreMap":264},[268,269,272,276,280,284,286,289,292,295,298,301],"span",{"class":270,"line":271},"line",1,[268,273,275],{"class":274},"sVt8B","cargo_home",[268,277,279],{"class":278},"szBVR","=",[268,281,283],{"class":282},"sZZnC","\"${",[268,285,231],{"class":274},[268,287,288],{"class":278},":-",[268,290,291],{"class":274},"$HOME",[268,293,294],{"class":278},"\u002F",[268,296,297],{"class":282},".",[268,299,300],{"class":274},"cargo",[268,302,303],{"class":282},"}\"\n",[268,305,307],{"class":270,"line":306},2,[268,308,310],{"emptyLinePlaceholder":309},true,"\n",[268,312,314,318,322,325,328],{"class":270,"line":313},3,[268,315,317],{"class":316},"sScJk","du",[268,319,321],{"class":320},"sj4cs"," -sh",[268,323,324],{"class":282}," target",[268,326,327],{"class":278}," 2>",[268,329,330],{"class":282},"\u002Fdev\u002Fnull\n",[268,332,334,336,338,341,344,347,349,351,354],{"class":270,"line":333},4,[268,335,317],{"class":316},[268,337,321],{"class":320},[268,339,340],{"class":282}," \"",[268,342,343],{"class":274},"$cargo_home",[268,345,346],{"class":282},"\u002Fregistry\u002Fcache\"",[268,348,340],{"class":282},[268,350,343],{"class":274},[268,352,353],{"class":282},"\u002Fregistry\u002Fsrc\"",[268,355,356],{"class":320}," \\\n",[268,358,360,363,365,368,370,372,375,377],{"class":270,"line":359},5,[268,361,362],{"class":282},"  \"",[268,364,343],{"class":274},[268,366,367],{"class":282},"\u002Fgit\u002Fdb\"",[268,369,340],{"class":282},[268,371,343],{"class":274},[268,373,374],{"class":282},"\u002Fgit\u002Fcheckouts\"",[268,376,327],{"class":278},[268,378,330],{"class":282},[11,380,381,382,385],{},"Cargo 也可能使用自訂的 target 資料夾。下列指令會輸出 workspace metadata，其中包含實際的 ",[15,383,384],{},"target_directory","：",[259,387,389],{"className":261,"code":388,"language":263,"meta":264,"style":264},"cargo metadata --no-deps --format-version 1\n",[15,390,391],{"__ignoreMap":264},[268,392,393,395,398,401,404],{"class":270,"line":271},[268,394,300],{"class":316},[268,396,397],{"class":282}," metadata",[268,399,400],{"class":320}," --no-deps",[268,402,403],{"class":320}," --format-version",[268,405,406],{"class":320}," 1\n",[11,408,409],{},"在 PowerShell 中，可以分別檢查目前專案與預設 Cargo Home：",[259,411,415],{"className":412,"code":413,"language":414,"meta":264,"style":264},"language-powershell shiki shiki-themes github-light github-dark","$CargoHome = if ($env:CARGO_HOME) { $env:CARGO_HOME } else { Join-Path $HOME \".cargo\" }\n\nGet-ChildItem .\\target -Recurse -File -Force -ErrorAction SilentlyContinue |\n  Measure-Object Length -Sum\nGet-ChildItem \"$CargoHome\\registry\\cache\" -Recurse -File -Force -ErrorAction SilentlyContinue |\n  Measure-Object Length -Sum\n","powershell",[15,416,417,422,426,431,436,441],{"__ignoreMap":264},[268,418,419],{"class":270,"line":271},[268,420,421],{},"$CargoHome = if ($env:CARGO_HOME) { $env:CARGO_HOME } else { Join-Path $HOME \".cargo\" }\n",[268,423,424],{"class":270,"line":306},[268,425,310],{"emptyLinePlaceholder":309},[268,427,428],{"class":270,"line":313},[268,429,430],{},"Get-ChildItem .\\target -Recurse -File -Force -ErrorAction SilentlyContinue |\n",[268,432,433],{"class":270,"line":333},[268,434,435],{},"  Measure-Object Length -Sum\n",[268,437,438],{"class":270,"line":359},[268,439,440],{},"Get-ChildItem \"$CargoHome\\registry\\cache\" -Recurse -File -Force -ErrorAction SilentlyContinue |\n",[268,442,444],{"class":270,"line":443},6,[268,445,435],{},[11,447,448],{},"PowerShell 會以位元組回報結果。更重要的是，這些檢查會讓你在刪除前再次確認正確位置。",[37,450,452],{"id":451},"如何安全清理專案-target-資料夾","如何安全清理專案 target 資料夾",[11,454,455,456,459],{},"先停止 ",[15,457,458],{},"cargo build","、測試、正在編譯的 rust-analyzer 工作，以及從該 workspace 啟動的程式。接著預覽 Cargo 準備移除的內容：",[259,461,463],{"className":261,"code":462,"language":263,"meta":264,"style":264},"cargo clean --dry-run -v\n",[15,464,465],{"__ignoreMap":264},[268,466,467,469,472,475],{"class":270,"line":271},[268,468,300],{"class":316},[268,470,471],{"class":282}," clean",[268,473,474],{"class":320}," --dry-run",[268,476,477],{"class":320}," -v\n",[11,479,480],{},"確認範圍正確後，清理目前 workspace 的完整 target 資料夾：",[259,482,484],{"className":261,"code":483,"language":263,"meta":264,"style":264},"cargo clean\n",[15,485,486],{"__ignoreMap":264},[268,487,488,490],{"class":270,"line":271},[268,489,300],{"class":316},[268,491,492],{"class":282}," clean\n",[11,494,495],{},"如果想保留仍有用的建置資料，可以縮小範圍：",[259,497,499],{"className":261,"code":498,"language":263,"meta":264,"style":264},"# 只移除 Release profile 的建置成果\ncargo clean --release\n\n# 只移除產生的文件\ncargo clean --doc\n\n# 只移除 workspace 中某個 package 的建置成果\ncargo clean -p your-package-name\n",[15,500,501,507,516,520,525,534,538,544],{"__ignoreMap":264},[268,502,503],{"class":270,"line":271},[268,504,506],{"class":505},"sJ8bj","# 只移除 Release profile 的建置成果\n",[268,508,509,511,513],{"class":270,"line":306},[268,510,300],{"class":316},[268,512,471],{"class":282},[268,514,515],{"class":320}," --release\n",[268,517,518],{"class":270,"line":313},[268,519,310],{"emptyLinePlaceholder":309},[268,521,522],{"class":270,"line":333},[268,523,524],{"class":505},"# 只移除產生的文件\n",[268,526,527,529,531],{"class":270,"line":359},[268,528,300],{"class":316},[268,530,471],{"class":282},[268,532,533],{"class":320}," --doc\n",[268,535,536],{"class":270,"line":443},[268,537,310],{"emptyLinePlaceholder":309},[268,539,541],{"class":270,"line":540},7,[268,542,543],{"class":505},"# 只移除 workspace 中某個 package 的建置成果\n",[268,545,547,549,551,554],{"class":270,"line":546},8,[268,548,300],{"class":316},[268,550,471],{"class":282},[268,552,553],{"class":320}," -p",[268,555,556],{"class":282}," your-package-name\n",[11,558,559,562,563,566,567,570],{},[15,560,561],{},"cargo clean"," 會遵循 Cargo 設定的 target 位置。對使用自訂 ",[15,564,565],{},"target-dir"," 的 workspace 而言，這比直接假設資料夾一定是 ",[15,568,569],{},".\u002Ftarget"," 更穩妥。",[11,572,573],{},"清理後資料夾再次出現很正常。下一次建置會重新建立它；因為增量編譯資料已經移除，第一次完整編譯通常會慢不少。",[37,575,577],{"id":576},"什麼時候才需要清理-cargo-共用快取","什麼時候才需要清理 Cargo 共用快取？",[11,579,580],{},"以下情況可以考慮清理：",[45,582,583,586,589,592],{},[48,584,585],{},"實際量測後，快取容量確實大到值得處理；",[48,587,588],{},"下載的壓縮檔或 Git 相依套件已損壞；",[48,590,591],{},"舊 toolchain 與專案留下近期不會再用的套件；",[48,593,594],{},"現在必須騰出空間，而且之後有穩定網路能夠復原。",[11,596,597,598,600],{},"搭飛機前、需要離線工作，或公司內部 registry 可能暫時無法連線時，不建議清理。也要先確認團隊是否使用自訂 registry、vendored dependencies 或非預設的 ",[15,599,231],{},"。",[11,602,603],{},"Cargo Home 官方文件把 registry 與 Git 相關內容視為可以透過重新解壓縮、checkout 或下載復原的快取。若決定手動刪除，請先結束 Cargo 相關程序，設定正確的 Cargo Home，並做最後一次檢查：",[259,605,607],{"className":261,"code":606,"language":263,"meta":264,"style":264},"cargo_home=\"${CARGO_HOME:-$HOME\u002F.cargo}\"\ndu -sh \"$cargo_home\u002Fregistry\u002Fcache\" \"$cargo_home\u002Fregistry\u002Fsrc\" \\\n  \"$cargo_home\u002Fgit\u002Fdb\" \"$cargo_home\u002Fgit\u002Fcheckouts\" 2>\u002Fdev\u002Fnull\n",[15,608,609,631,651],{"__ignoreMap":264},[268,610,611,613,615,617,619,621,623,625,627,629],{"class":270,"line":271},[268,612,275],{"class":274},[268,614,279],{"class":278},[268,616,283],{"class":282},[268,618,231],{"class":274},[268,620,288],{"class":278},[268,622,291],{"class":274},[268,624,294],{"class":278},[268,626,297],{"class":282},[268,628,300],{"class":274},[268,630,303],{"class":282},[268,632,633,635,637,639,641,643,645,647,649],{"class":270,"line":306},[268,634,317],{"class":316},[268,636,321],{"class":320},[268,638,340],{"class":282},[268,640,343],{"class":274},[268,642,346],{"class":282},[268,644,340],{"class":282},[268,646,343],{"class":274},[268,648,353],{"class":282},[268,650,356],{"class":320},[268,652,653,655,657,659,661,663,665,667],{"class":270,"line":313},[268,654,362],{"class":282},[268,656,343],{"class":274},[268,658,367],{"class":282},[268,660,340],{"class":282},[268,662,343],{"class":274},[268,664,374],{"class":282},[268,666,327],{"class":278},[268,668,330],{"class":282},[11,670,671],{},"接著只刪除自己明確選定的快取子資料夾：",[259,673,675],{"className":261,"code":674,"language":263,"meta":264,"style":264},"rm -rf \"$cargo_home\u002Fregistry\u002Fcache\" \"$cargo_home\u002Fregistry\u002Fsrc\" \\\n  \"$cargo_home\u002Fgit\u002Fdb\" \"$cargo_home\u002Fgit\u002Fcheckouts\"\n",[15,676,677,699],{"__ignoreMap":264},[268,678,679,682,685,687,689,691,693,695,697],{"class":270,"line":271},[268,680,681],{"class":316},"rm",[268,683,684],{"class":320}," -rf",[268,686,340],{"class":282},[268,688,343],{"class":274},[268,690,346],{"class":282},[268,692,340],{"class":282},[268,694,343],{"class":274},[268,696,353],{"class":282},[268,698,356],{"class":320},[268,700,701,703,705,707,709,711],{"class":270,"line":306},[268,702,362],{"class":282},[268,704,343],{"class":274},[268,706,367],{"class":282},[268,708,340],{"class":282},[268,710,343],{"class":274},[268,712,713],{"class":282},"\u002Fgit\u002Fcheckouts\"\n",[11,715,716,717,720],{},"這個指令不會經過垃圾桶，絕對不要把它簡化成 ",[15,718,719],{},"rm -rf ~\u002F.cargo","。完成後，下一次連網建置可能需要重新下載並解壓縮相依套件。",[11,722,723,724,727,728,730,731,734],{},"Windows 使用者可以透過檔案總管，檢查並刪除 ",[15,725,726],{},"%CARGO_HOME%"," 或 ",[15,729,227],{}," 下對應的快取子資料夾。用圖形介面逐項確認，比較不容易把 ",[15,732,733],{},"bin","、設定或認證檔案一起選進去。",[37,736,738],{"id":737},"哪些內容不能當作-cargo-快取清理","哪些內容不能當作 Cargo 快取清理？",[11,740,741],{},"不要把以下內容列為清理目標：",[45,743,744,757,763,769,782],{},[48,745,746,749,750,207,753,756],{},[15,747,748],{},".cargo\u002Fbin","：這裡存放 ",[15,751,752],{},"cargo-audit",[15,754,755],{},"cargo-edit"," 等已安裝指令；",[48,758,759,762],{},[15,760,761],{},".cargo\u002Fcredentials.toml","：這裡可能存放 registry 登入 token；",[48,764,765,768],{},[15,766,767],{},".cargo\u002Fconfig.toml","：這裡可能定義 registry、alias、網路設定與編譯目標行為；",[48,770,771,772,207,774,207,776,727,779,781],{},"專案裡的 ",[15,773,206],{},[15,775,210],{},[15,777,778],{},"build.rs",[15,780,213],{},"；",[48,783,784],{},"vendored dependencies 或團隊維護的離線 mirror，除非負責人已有復原計畫。",[11,786,787,788,790],{},"如果不確定某個資料夾是否只是快取，就停在檢查步驟。位於 ",[15,789,24],{}," 底下，不代表它可以隨意刪除。",[37,792,794],{"id":793},"使用-mangodisk-檢查-rust-建置成果","使用 MangoDisk 檢查 Rust 建置成果",[11,796,797,802,803,805,806,808],{},[798,799,801],"a",{"href":800},"\u002Ftw\u002Fdocs\u002Ffeatures\u002Fdeep-clean","MangoDisk 深度清理","可以辨識 Rust 專案的 ",[15,804,17],{}," 資料夾，以及各平台對應的 Cargo 快取位置。規則不會把整個 ",[15,807,24],{}," 當成清理目標，專案建置成果也不會預設勾選。",[11,810,811,812,814,815,600],{},"掃描會在本機完成。你可以先查看路徑與實際容量，再決定是否刪除；當多個 workspace 都有自己的 ",[15,813,17],{}," 時特別實用。完整的確認與清理記錄流程可參考 ",[798,816,818],{"href":817},"\u002Ftw\u002Fdocs\u002Fsafety","MangoDisk 安全指南",[37,820,821],{"id":821},"常見問題",[823,824,826],"h3",{"id":825},"rust-專案的-target-資料夾可以安全刪除嗎","Rust 專案的 target 資料夾可以安全刪除嗎？",[11,828,829],{},"可以，前提是它確實是 Cargo 設定的建置輸出位置，而且目前沒有建置工作。裡面是可重新產生的成果，不是專案原始碼；刪除後要預期第一次完整編譯會比較久。",[823,831,833],{"id":832},"cargo-clean-會清掉-cargo-的下載快取嗎","cargo clean 會清掉 Cargo 的下載快取嗎？",[11,835,836,837,839],{},"不會。",[15,838,561],{}," 移除的是 target 資料夾中的建置成果，不會清空 Cargo Home 裡的 registry 或 Git 相依套件快取。",[823,841,843],{"id":842},"可以刪除-cargolock-來省空間或修復相依套件嗎","可以刪除 Cargo.lock 來省空間或修復相依套件嗎？",[11,845,846,847,849],{},"不可以。",[15,848,210],{}," 很小，用來記錄已解析的相依套件版本。刪除它不是磁碟清理，還可能讓 Cargo 選到不同版本。",[823,851,853],{"id":852},"為什麼-cargo-快取和-target-又出現了","為什麼 Cargo 快取和 target 又出現了？",[11,855,856],{},"這是正常現象。專案建置時，Cargo 會重新產生建置成果並復原缺少的相依資料。清理只會移除舊的可再生資料，不會停用快取機制。",[37,858,859],{"id":859},"資料來源與延伸閱讀",[45,861,862,870,877,884,890],{},[48,863,864],{},[798,865,869],{"href":866,"rel":867},"https:\u002F\u002Fdoc.rust-lang.org\u002Fstable\u002Fcargo\u002Freference\u002Fbuild-cache.html",[868],"nofollow","Cargo Book：Build Cache",[48,871,872],{},[798,873,876],{"href":874,"rel":875},"https:\u002F\u002Fdoc.rust-lang.org\u002Fcargo\u002Fcommands\u002Fcargo-clean.html",[868],"Cargo Book：cargo clean",[48,878,879],{},[798,880,883],{"href":881,"rel":882},"https:\u002F\u002Fdoc.rust-lang.org\u002Fcargo\u002Fguide\u002Fcargo-home.html",[868],"Cargo Book：Cargo Home",[48,885,886],{},[798,887,889],{"href":888},"\u002Ftw\u002Fblog\u002Fhow-to-clear-xcode-derived-data-safely","如何安全刪除 Xcode Derived Data",[48,891,892],{},[798,893,895],{"href":894},"\u002Ftw\u002Fblog\u002Fwhy-i-built-mangodisk","我為什麼開發 MangoDisk",[11,897,898,899,903],{},"想先看清楚 Rust 建置成果與 Cargo 快取，再決定要不要刪除？可以",[798,900,902],{"href":901},"\u002Ftw\u002F","下載 MangoDisk","，直接在本機檢查掃描結果。",[905,906,907],"style",{},"html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}",{"title":264,"searchDepth":306,"depth":306,"links":909},[910,911,912,913,914,915,916,917,923],{"id":39,"depth":306,"text":40},{"id":235,"depth":306,"text":236},{"id":254,"depth":306,"text":254},{"id":451,"depth":306,"text":452},{"id":576,"depth":306,"text":577},{"id":737,"depth":306,"text":738},{"id":793,"depth":306,"text":794},{"id":821,"depth":306,"text":821,"children":918},[919,920,921,922],{"id":825,"depth":313,"text":826},{"id":832,"depth":313,"text":833},{"id":842,"depth":313,"text":843},{"id":852,"depth":313,"text":853},{"id":859,"depth":306,"text":859},"開發者磁碟清理","\u002Fimages\u002Fblog\u002Fcargo-cache-vs-target-folder.webp","將 Rust 相依套件與專案建置成果分開檢查後再安全清理","了解 Rust 專案 target 建置成果與 Cargo 相依套件快取的差異、哪些可以安全刪除，以及 .cargo 裡哪些內容不該當成快取清理",false,"md",{},"\u002Ftw\u002Fblog\u002Fcargo-cache-vs-target-folder","2026-08-12T00:00:00+08:00",{"title":5,"description":927},"tw\u002Fblog\u002Fcargo-cache-vs-target-folder",[936,937,561,924],"Cargo 快取","Rust target 資料夾","article-cargo-cache-vs-target-folder","9lYVBZJ_z4ZteA3yn6SrC5_pJzNvbkwEyQ0Ebo6Pjas",1786706051528]