[{"data":1,"prerenderedAt":3159},["ShallowReactive",2],{"all-posts":3,"post:\u002Fithome-2026-day-30":1210},[4,23,35,46,57,68,80,91,102,114,126,138,149,160,171,182,193,204,215,226,237,248,258,268,278,288,298,308,319,330,341,354,368,380,390,400,411,421,431,441,451,461,471,481,491,501,511,521,531,541,551,561,571,581,591,601,611,621,631,641,651,661,675,691,704,719,731,742,752,762,772,782,792,802,812,822,832,842,852,862,871,881,891,901,911,921,931,941,951,961,971,980,990,1000,1010,1020,1036,1050,1062,1073,1083,1095,1107,1121,1134,1145,1156,1167,1180,1191,1201],{"path":5,"title":6,"description":7,"date":8,"updated":9,"tags":10,"categories":14,"draft":15,"wordCount":16,"readingTime":17,"canonical":18,"series":19},"\u002Fithome-2026-day-30","Day 30：Angular Router Providers 與生命週期管理，路由離開後 Service 會銷毀嗎？","平常在 Angular 中，我們可以透過 providers 決定 Service 的注入範圍。例如註冊在 Root，讓整個 Application 共用同一個實例；或註冊在 Component，讓 Service 隨著…","2026-10-14T14:46:39+08:00",null,[11,12,13],"iThome 鐵人賽","2026 鐵人賽","Angular",[11,13],false,7227,7,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10424222",{"name":20,"url":21,"day":22},"2026 iThome 鐵人賽：Angular 22 Signal 進化論","https:\u002F\u002Fithelp.ithome.com.tw\u002Fusers\u002F20116554\u002Fironman\u002F9939",30,{"path":24,"title":25,"description":26,"date":27,"updated":9,"tags":28,"categories":29,"draft":15,"wordCount":30,"readingTime":31,"canonical":32,"series":33},"\u002Fithome-2026-day-29","Day 29：Angular 也有 VueUse？使用 Signality 整合常見 Browser API","在 Vue 生態系中，VueUse 提供許多 Composables，讓我們可以快速使用瀏覽器功能，例如監聽網路狀態、保存使用者設定，或偵測元素是否進入可視範圍。","2026-10-13T23:14:18+08:00",[11,12,13],[11,13],6387,6,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10424070",{"name":20,"url":21,"day":34},29,{"path":36,"title":37,"description":38,"date":39,"updated":9,"tags":40,"categories":41,"draft":15,"wordCount":42,"readingTime":31,"canonical":43,"series":44},"\u002Fithome-2026-day-28","Day 28：Angular 動態建立 Component，NgComponentOutlet 與 ViewContainerRef","平常在 Angular 中使用 Component，通常會直接在 Template 裡面宣告：","2026-10-12T17:27:41+08:00",[11,12,13],[11,13],6565,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10423641",{"name":20,"url":21,"day":45},28,{"path":47,"title":48,"description":49,"date":50,"updated":9,"tags":51,"categories":52,"draft":15,"wordCount":53,"readingTime":17,"canonical":54,"series":55},"\u002Fithome-2026-day-27","Day 27：NgRx Store vs SignalStore，從 Action、Reducer 到直接更新 State","前幾天我們使用 NgRx SignalStore 實作購物車，透過 withState() 管理商品資料、withComputed() 計算總金額，再利用 withMethods() 與 patchState() 更新 …","2026-10-11T20:06:41+08:00",[11,12,13],[11,13],7308,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10423362",{"name":20,"url":21,"day":56},27,{"path":58,"title":59,"description":60,"date":61,"updated":9,"tags":62,"categories":63,"draft":15,"wordCount":64,"readingTime":17,"canonical":65,"series":66},"\u002Fithome-2026-day-26","Day 26：SignalStore 與 Strategy Pattern，透過 DI 動態切換業務邏輯","昨天我們使用 Angular 原生 Signal 與 NgRx SignalStore 實作購物車，透過 State 管理商品資料，再利用 Computed 計算商品數量與總金額。","2026-10-10T22:01:59+08:00",[11,12,13],[11,13],7347,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10423116",{"name":20,"url":21,"day":67},26,{"path":69,"title":70,"description":71,"date":72,"updated":9,"tags":73,"categories":74,"draft":15,"wordCount":75,"readingTime":76,"canonical":77,"series":78},"\u002Fithome-2026-day-25","Day 25：Angular SignalStore，原生 Signal 不夠用嗎？","在 Angular 開發中，如果資料只會被單一 Component 使用，通常可以直接透過 signal() 管理。但當多個 Component 需要共用同一份資料時，就得考慮狀態應該放在哪裡。","2026-10-09T21:28:45+08:00",[11,12,13],[11,13],9117,9,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10422784",{"name":20,"url":21,"day":79},25,{"path":81,"title":82,"description":83,"date":84,"updated":9,"tags":85,"categories":86,"draft":15,"wordCount":87,"readingTime":31,"canonical":88,"series":89},"\u002Fithome-2026-day-24","Day 24：SPA Router 為什麼不再只靠 History API？","平常使用 Angular Router 時，可以透過 routerLink 或 router.navigate() 切換不同頁面。","2026-10-08T14:30:47+08:00",[11,12,13],[11,13],6330,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10422348",{"name":20,"url":21,"day":90},24,{"path":92,"title":93,"description":94,"date":95,"updated":9,"tags":96,"categories":97,"draft":15,"wordCount":98,"readingTime":17,"canonical":99,"series":100},"\u002Fithome-2026-day-23","Day 23：RouteReuseStrategy，切換路由一定要銷毀 Component 嗎？","在後台系統中，很常會看到頁籤式介面，例如：","2026-10-07T15:58:32+08:00",[11,12,13],[11,13],7361,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10422016",{"name":20,"url":21,"day":101},23,{"path":103,"title":104,"description":105,"date":106,"updated":9,"tags":107,"categories":108,"draft":15,"wordCount":109,"readingTime":110,"canonical":111,"series":112},"\u002Fithome-2026-day-22","Day 22：Angular Render Lifecycle，從 afterNextRender 到 DestroyRef","過去在 Angular 中，只要遇到初始化、View 建立或資源清理，通常會先想到 Lifecycle Hooks：","2026-10-06T23:36:23+08:00",[11,12,13],[11,13],8111,8,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10421810",{"name":20,"url":21,"day":113},22,{"path":115,"title":116,"description":117,"date":118,"updated":9,"tags":119,"categories":120,"draft":15,"wordCount":121,"readingTime":122,"canonical":123,"series":124},"\u002Fithome-2026-day-21","Day 21：Angular Template 還適合呼叫 Method 嗎？從 Pipe、RxJS 到 computed","過去在寫 Angular 時，因為 Template 可以直接呼叫 Method，很容易在專案裡看到大量這樣的寫法。","2026-10-05T23:30:32+08:00",[11,12,13],[11,13],5431,5,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10421425",{"name":20,"url":21,"day":125},21,{"path":127,"title":128,"description":129,"date":130,"updated":9,"tags":131,"categories":132,"draft":15,"wordCount":133,"readingTime":134,"canonical":135,"series":136},"\u002Fithome-2026-day-20","Day 20：Signal Forms 非同步驗證，validateHttp 與 validateAsync","前兩篇介紹了 Signal Forms 的基本驗證，以及需要參考其他欄位的 Cross-field Validation。","2026-10-04T20:56:17+08:00",[11,12,13],[11,13],4278,4,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10420910",{"name":20,"url":21,"day":137},20,{"path":139,"title":140,"description":141,"date":142,"updated":9,"tags":143,"categories":144,"draft":15,"wordCount":145,"readingTime":134,"canonical":146,"series":147},"\u002Fithome-2026-day-19","Day 19：Signal Forms Cross-field Validation 與欄位更新時機","上一篇介紹 Signal Forms 時，已經看到可以透過 Schema 定義欄位驗證，例如 required()、email()、minLength()。","2026-10-03T23:18:26+08:00",[11,12,13],[11,13],3783,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10420631",{"name":20,"url":21,"day":148},19,{"path":150,"title":151,"description":152,"date":153,"updated":9,"tags":154,"categories":155,"draft":15,"wordCount":156,"readingTime":31,"canonical":157,"series":158},"\u002Fithome-2026-day-18","Day 18：Angular Signal Forms 穩定了，跟我們用了這麼久的 Reactive Forms 到底差在哪？","在 Angular 中處理表單，很多專案使用的都是 Reactive Forms。","2026-10-02T23:28:36+08:00",[11,12,13],[11,13],5886,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10420249",{"name":20,"url":21,"day":159},18,{"path":161,"title":162,"description":163,"date":164,"updated":9,"tags":165,"categories":166,"draft":15,"wordCount":167,"readingTime":31,"canonical":168,"series":169},"\u002Fithome-2026-day-17","Day 17：effect() 不是拿來同步 Signal 的，Angular 的 Side Effect 該怎麼寫？","effect() 是 Angular signal 裡很容易被誤用的一個 API。因為寫法直覺，只要讀取 signal，就能在值改變時執行一些事情，所以很常被拿來同步狀態、打 API，甚至再去修改其他 signal。","2026-10-01T21:22:13+08:00",[11,12,13],[11,13],6473,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10419779",{"name":20,"url":21,"day":170},17,{"path":172,"title":173,"description":174,"date":175,"updated":9,"tags":176,"categories":177,"draft":15,"wordCount":178,"readingTime":31,"canonical":179,"series":180},"\u002Fithome-2026-day-16","Day 16：即將登場的 Route Resources，Angular Router 為什麼需要新的資料載入方式？","過去在 Angular Router 中，如果希望進入 Component 前先完成資料載入，可以透過 Resolver，讓資料取得流程在 Component 初始化之前執行。","2026-09-30T23:12:05+08:00",[11,12,13],[11,13],6534,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10419409",{"name":20,"url":21,"day":181},16,{"path":183,"title":184,"description":185,"date":186,"updated":9,"tags":187,"categories":188,"draft":15,"wordCount":189,"readingTime":17,"canonical":190,"series":191},"\u002Fithome-2026-day-15","Day 15：搞懂 Injection Context，從 inject()、runInInjectionContext() 到 injectAsync()","前面提到 Injection Context 時，可能會讓人聯想到先前介紹過的 Reactive Context。我一開始也有點搞混，因此花了一些時間重新理解 Angular 裡這些不同的執行環境。","2026-09-29T13:44:28+08:00",[11,12,13],[11,13],6986,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10418752",{"name":20,"url":21,"day":192},15,{"path":194,"title":195,"description":196,"date":197,"updated":9,"tags":198,"categories":199,"draft":15,"wordCount":200,"readingTime":17,"canonical":201,"series":202},"\u002Fithome-2026-day-14","Day 14：Lazy Loading 不只一種，從 Router Preloading、@defer 到 injectAsync()","當 Client Side Rendering 的應用越來越大時，我們通常會開始思考，能不能把原本一次載入的內容拆得更小，等到真正需要時再下載，避免初始載入過多 JavaScript，拉長畫面呈現的時間。","2026-09-28T22:44:46+08:00",[11,12,13],[11,13],7674,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10418485",{"name":20,"url":21,"day":203},14,{"path":205,"title":206,"description":207,"date":208,"updated":9,"tags":209,"categories":210,"draft":15,"wordCount":211,"readingTime":110,"canonical":212,"series":213},"\u002Fithome-2026-day-13","Day 13：從 Router Event 到 Signal","路由狀態管理在前端開發中比較少被單獨拿出來討論，但在 Angular 裡，一次路由導航其實會經過不少階段，也會在過程中發出不同的 Router Event，例如 NavigationStart、NavigationEnd…","2026-09-27T20:37:55+08:00",[11,12,13],[11,13],7777,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10417948",{"name":20,"url":21,"day":214},13,{"path":216,"title":217,"description":218,"date":219,"updated":9,"tags":220,"categories":221,"draft":15,"wordCount":222,"readingTime":122,"canonical":223,"series":224},"\u002Fithome-2026-day-12","Day 12：從 httpResource 到 TanStack Query，認識 Server State","前面我們花了不少時間討論，為什麼「請求本身的狀態」和「元件的顯示狀態」應該分開處理。","2026-09-26T23:35:12+08:00",[11,12,13],[11,13],5119,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10417614",{"name":20,"url":21,"day":225},12,{"path":227,"title":228,"description":229,"date":230,"updated":9,"tags":231,"categories":232,"draft":15,"wordCount":233,"readingTime":122,"canonical":234,"series":235},"\u002Fithome-2026-day-11","Day 11：用 rxResource 串起 Observable 與 Resource","前面介紹了不少 Resource 到 httpResource() 的應用。不過在 Angular 開發中，Observable 與 RxJS 仍然是很常見的非同步資料處理方式，像是 switchMap、map、debo…","2026-09-25T22:42:04+08:00",[11,12,13],[11,13],4908,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10417143",{"name":20,"url":21,"day":236},11,{"path":238,"title":239,"description":240,"date":241,"updated":9,"tags":242,"categories":243,"draft":15,"wordCount":244,"readingTime":31,"canonical":245,"series":246},"\u002Fithome-2026-day-10","Day 10：linkedSignal 讓相依狀態也能被修改","昨天我們透過 httpResource() 搭配 chain() 處理兩個非同步資料之間的依賴。下游 Request 需要使用上游資料時，會等上游完成後再繼續；當 Request 的來源改變，Resource 的狀態也會…","2026-09-24T23:49:49+08:00",[11,12,13],[11,13],5623,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10416746",{"name":20,"url":21,"day":247},10,{"path":249,"title":250,"description":251,"date":252,"updated":9,"tags":253,"categories":254,"draft":15,"wordCount":255,"readingTime":134,"canonical":256,"series":257},"\u002Fithome-2026-day-09","Day 9：httpResource 實務篇，統一回覆格式與 chain 相依請求","昨天我們透過 Orval 串起 API Contract，了解如何根據 OpenAPI 規格產生前端需要的型別與 API 呼叫方式。","2026-09-23T23:42:40+08:00",[11,12,13],[11,13],4358,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10416227",{"name":20,"url":21,"day":76},{"path":259,"title":260,"description":261,"date":262,"updated":9,"tags":263,"categories":264,"draft":15,"wordCount":265,"readingTime":122,"canonical":266,"series":267},"\u002Fithome-2026-day-08","Day 8：用 Orval 串起 Angular API Contract，同時產生 HttpClient、httpResource 與 Zod","前後端在對接 API 時，常見的問題之一，就是雙方對資料格式的定義逐漸不一致。","2026-09-22T23:48:12+08:00",[11,12,13],[11,13],4451,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10415694",{"name":20,"url":21,"day":110},{"path":269,"title":270,"description":271,"date":272,"updated":9,"tags":273,"categories":274,"draft":15,"wordCount":275,"readingTime":17,"canonical":276,"series":277},"\u002Fithome-2026-day-07","Day 7：從 Resource 到 httpResource，用 Signal 管理 HTTP 資料請求","昨天我們提到，Resource API 本身是一套通用的非同步資料模型，比較適合用在「讀取資料」這類情境，而不是新增、修改或刪除資料這種 Mutation 操作。","2026-09-21T22:13:18+08:00",[11,12,13],[11,13],6735,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10415038",{"name":20,"url":21,"day":17},{"path":279,"title":280,"description":281,"date":282,"updated":9,"tags":283,"categories":284,"draft":15,"wordCount":285,"readingTime":122,"canonical":286,"series":287},"\u002Fithome-2026-day-06","Day 6：Resource API，把非同步資料帶進 Signal","今天來看 Angular Signal 裡一個很重要的非同步資料 API：Resource API。","2026-09-20T19:25:37+08:00",[11,12,13],[11,13],5054,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10414377",{"name":20,"url":21,"day":31},{"path":289,"title":290,"description":291,"date":292,"updated":9,"tags":293,"categories":294,"draft":15,"wordCount":295,"readingTime":134,"canonical":296,"series":297},"\u002Fithome-2026-day-05","Day 5：從 Reactive Graph 到 View Tree，看 Angular 如何找到真正需要更新的畫面","前面我們已經知道，當 Signal 的值發生變化後，Angular 會透過 Reactive Graph 找到受到影響的 Consumer。","2026-09-19T20:19:47+08:00",[11,12,13],[11,13],4364,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10413852",{"name":20,"url":21,"day":122},{"path":299,"title":300,"description":301,"date":302,"updated":9,"tags":303,"categories":304,"draft":15,"wordCount":305,"readingTime":122,"canonical":306,"series":307},"\u002Fithome-2026-day-04","Day 4：Angular 怎麼知道誰正在讀 Signal？從 Reactive Context 理解依賴追蹤","前面我們看過，當 Template 讀取 Signal 時，Angular 會記住「誰依賴了誰」；當 Signal 發生變化後，也會透過 Reactive Graph 通知相關的 Consumer。","2026-09-18T21:58:16+08:00",[11,12,13],[11,13],4894,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10413313",{"name":20,"url":21,"day":134},{"path":309,"title":310,"description":311,"date":312,"updated":9,"tags":313,"categories":314,"draft":15,"wordCount":315,"readingTime":122,"canonical":316,"series":317},"\u002Fithome-2026-day-03","Day 3：從 set()、update() 看懂 Angular Signal 的基本使用與更新機制","昨天我們先試著理解，在 Template 中使用 Signal() 時，Angular 是如何建立依賴關係，並在 Signal 發生變化後，知道哪些 View 可能受到影響。","2026-09-17T23:08:58+08:00",[11,12,13],[11,13],5451,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10412826",{"name":20,"url":21,"day":318},3,{"path":320,"title":321,"description":322,"date":323,"updated":9,"tags":324,"categories":325,"draft":15,"wordCount":326,"readingTime":134,"canonical":327,"series":328},"\u002Fithome-2026-day-02","Day 2：Angular Signal 是什麼？從 Change Detection 理解它的運作原理","傳統 Angular 在監測資料變化時，通常會搭配 zone.js。像是 DOM 事件、Promise、Timer、HTTP 請求這些非同步操作發生時，zone.js 會幫忙攔截。","2026-09-16T20:19:12+08:00",[11,12,13],[11,13],4276,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10411944",{"name":20,"url":21,"day":329},2,{"path":331,"title":332,"description":333,"date":334,"updated":9,"tags":335,"categories":336,"draft":15,"wordCount":337,"readingTime":329,"canonical":338,"series":339},"\u002Fithome-2026-day-01","Day 1：為什麼想聊 Angular Signal？","相信講到前端框架，大家第一時間想到的通常會是 Vue、React，甚至也有人會推薦 Svelte 這類近年討論度很高的框架。但一講到 Angular，很多人的第一印象可能就像看到一座大城堡一樣：東西很多、規則很多，一時之…","2026-09-15T23:56:26+08:00",[11,12,13],[11,13],1478,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10411425",{"name":20,"url":21,"day":340},1,{"path":342,"title":343,"description":344,"date":345,"updated":9,"tags":346,"categories":351,"draft":15,"wordCount":353,"readingTime":134,"canonical":9,"series":9},"\u002FTS-Excess-Property-Checks","TypeScript 踩坑筆記：物件字面量的多餘屬性檢查機制","深入探討 TypeScript 的多餘屬性檢查（Excess Property Checks）機制，解析物件字面量與變數賦值的型別檢查差異，並提供實務開發中避免型別陷阱的最佳實踐方法。","2026-01-31T16:29:23+08:00",[347,348,349,350],"Excess Property Checks","Structural Typing","Type Safety","NestJS",[352],"TypeScript",3551,{"path":355,"title":356,"description":357,"date":358,"updated":9,"tags":359,"categories":361,"draft":15,"wordCount":363,"readingTime":329,"canonical":364,"series":365},"\u002Fithome-2025-day-30","Day 30：開發之旅完結 - 感謝與展望","終於來到鐵人賽的最後一天！這是我第二次參加鐵人賽，今年的主題是 LINE Bot 開發。這個主題源自於我參加的十二週讀書會分享，當時我發現大家對 LINE Bot 很感興趣，而我自己也一直很喜歡這個主題，於是早在六月就定…","2025-10-13T20:11:12+08:00",[11,360],"2025 鐵人賽",[11,362],"Line Bot",1751,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10396850",{"name":366,"url":367,"day":22},"2025 iThome 鐵人賽：Line Bot × NestJS：30 天開發日記","https:\u002F\u002Fithelp.ithome.com.tw\u002Fusers\u002F20116554\u002Fironman\u002F8779",{"path":369,"title":370,"description":371,"date":372,"updated":9,"tags":373,"categories":376,"draft":15,"wordCount":377,"readingTime":31,"canonical":378,"series":379},"\u002Fithome-2025-day-29","Day 29：LIFF 會員註冊 - 信箱驗證與 Swagger 文件整合","延續 Day 28 會員註冊的流程，在實際的會員註冊場景中，電子信箱驗證是確保用戶身份真實性的重要環節。本篇將基於昨天的註冊流程，新增兩個核心 API：發送驗證信與驗證驗證碼，讓會員註冊功能更加完整且安全。","2025-10-12T23:15:00+08:00",[11,360,362,374,350,375],"LIFF","Swagger",[11,362],6089,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10396512",{"name":366,"url":367,"day":34},{"path":381,"title":382,"description":383,"date":384,"updated":9,"tags":385,"categories":386,"draft":15,"wordCount":387,"readingTime":122,"canonical":388,"series":389},"\u002Fithome-2025-day-28","Day 28：LIFF 會員註冊 - ID Token 驗證與資料庫整合","今天的開發重點是建立會員卡系統，將 LIFF 前端與 NestJS 後端完整串接。","2025-10-11T22:57:29+08:00",[11,360,362,374,350],[11,362],5254,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10396146",{"name":366,"url":367,"day":45},{"path":391,"title":392,"description":393,"date":394,"updated":9,"tags":395,"categories":396,"draft":15,"wordCount":397,"readingTime":318,"canonical":398,"series":399},"\u002Fithome-2025-day-27","Day 27：群組事件與檔案訊息接收","今天主要補充 LINE Bot 在群組中的專屬特性，包括群組限定的 Webhook 事件，以及前面提到但尚未說明的第 7 種訊息類型 file 檔案訊息。","2025-10-10T21:01:52+08:00",[11,360,362,350],[11,362],2888,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10395785",{"name":366,"url":367,"day":56},{"path":401,"title":402,"description":403,"date":404,"updated":9,"tags":405,"categories":407,"draft":15,"wordCount":408,"readingTime":122,"canonical":409,"series":410},"\u002Fithome-2025-day-26","Day 26：LINE Pay 線上付款","LINE Pay 提供兩種付款方式：線上付款與實體付款。實體付款主要採用店家出示條碼的模式，顧客掃描後即可輸入金額完成付款。這兩種付款方式都支援在沙盒(Sandbox)環境中進行測試。本文將著重說明線上付款的整合流程。","2025-10-09T23:39:32+08:00",[11,360,406],"Line Pay",[11,362],4876,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10395481",{"name":366,"url":367,"day":67},{"path":412,"title":413,"description":414,"date":415,"updated":9,"tags":416,"categories":417,"draft":15,"wordCount":418,"readingTime":318,"canonical":419,"series":420},"\u002Fithome-2025-day-25","Day 25：優惠券設定與 Coupon Message 實作","LINE Official Account 的「優惠券」是提升顧客互動與忠誠度的重要功能。透過獎勵機制，不僅能吸引新客，更能有效促進回購。","2025-10-08T23:49:32+08:00",[11,360,362,350],[11,362],3207,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10395076",{"name":366,"url":367,"day":79},{"path":422,"title":423,"description":424,"date":425,"updated":9,"tags":426,"categories":427,"draft":15,"wordCount":428,"readingTime":134,"canonical":429,"series":430},"\u002Fithome-2025-day-24","Day 24：LIFF 刮刮樂實戰體驗","在了解 LIFF 的基礎設計流程後，本文將透過「刮刮樂」案例示範 LIFF API 的實際應用。從啟動時檢查權限與執行環境、確認用戶分享功能權限，到刮刮樂結束後發送訊息並關閉 LIFF，完整呈現 LIFF 在互動應用中的…","2025-10-07T22:36:58+08:00",[11,360,362,374],[11,362],4200,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10394618",{"name":366,"url":367,"day":90},{"path":432,"title":433,"description":434,"date":435,"updated":9,"tags":436,"categories":437,"draft":15,"wordCount":438,"readingTime":134,"canonical":439,"series":440},"\u002Fithome-2025-day-23","Day 23：LIFF 網頁應用開發入門","在鐵人賽前半段，我們深入探討了 LINE Bot 的兩大核心功能：Richmenu(選單設置)與各種 Reply Message(回覆訊息)的訊息類型。然而在實務應用中，若要提供更豐富的互動體驗，Line 往往需要搭配 …","2025-10-06T23:06:57+08:00",[11,360,362,374],[11,362],4400,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10394035",{"name":366,"url":367,"day":101},{"path":442,"title":443,"description":444,"date":445,"updated":9,"tags":446,"categories":447,"draft":15,"wordCount":448,"readingTime":329,"canonical":449,"series":450},"\u002Fithome-2025-day-22","Day 22：Render 雲端平台部署 Nest 後端伺服器","今天的目標是將系統正式上線。經過這段時間的開發，我們已完成 Line Message API 的核心功能與日誌處理機制。","2025-10-05T22:52:11+08:00",[11,360,362,350],[11,362],1895,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10393809",{"name":366,"url":367,"day":113},{"path":452,"title":453,"description":454,"date":455,"updated":9,"tags":456,"categories":457,"draft":15,"wordCount":458,"readingTime":318,"canonical":459,"series":460},"\u002Fithome-2025-day-21","Day 21：Nest Pino 整合 Grafana Loki 日誌","Loki 環境變數可參考 Day 20 文章的 Grafana Data Source settings 設定","2025-10-04T17:24:26+08:00",[11,360,362,350],[11,362],2740,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10393305",{"name":366,"url":367,"day":125},{"path":462,"title":463,"description":464,"date":465,"updated":9,"tags":466,"categories":467,"draft":15,"wordCount":468,"readingTime":318,"canonical":469,"series":470},"\u002Fithome-2025-day-20","Day 20：Grafana Loki 日誌服務 - 從申請到 API 串接測試","目前已經理解了 LINE Messaging API 的核心功能，包括如何接收訊息、串接第三方服務，以及發送多種類型的訊息。接下來，我們將把原本架設在 ngrok 的後端伺服器，透過 GitHub 自動化部署到 Rend…","2025-10-03T23:16:16+08:00",[11,360,362,350],[11,362],2461,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10392910",{"name":366,"url":367,"day":137},{"path":472,"title":473,"description":474,"date":475,"updated":9,"tags":476,"categories":477,"draft":15,"wordCount":478,"readingTime":318,"canonical":479,"series":480},"\u002Fithome-2025-day-19","Day 19：Flex Message Carousel 食譜分享","Flex Message 可以分成 bubble(單張卡片) 跟 carousel(多張卡片輪播) 兩種方式，昨天示範了 bubble 格式的電子個人名片後，今天主要展示 carousel 的應用，兩者的基本結構大致相同…","2025-10-02T16:06:17+08:00",[11,360,362,350],[11,362],2267,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10392256",{"name":366,"url":367,"day":148},{"path":482,"title":483,"description":484,"date":485,"updated":9,"tags":486,"categories":487,"draft":15,"wordCount":488,"readingTime":122,"canonical":489,"series":490},"\u002Fithome-2025-day-18","Day 18：Flex Message 設計個人名片","從基礎的文字互動開始，我們逐步探索了六大核心訊息類型的發送機制、Template Message 的結構化設計，以及 ImageMap Message 的互動式體驗。今天，我們將進入 LINE Bot 最具彈性的訊息格式…","2025-10-01T17:57:47+08:00",[11,360,362,350],[11,362],4468,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10391723",{"name":366,"url":367,"day":159},{"path":492,"title":493,"description":494,"date":495,"updated":9,"tags":496,"categories":497,"draft":15,"wordCount":498,"readingTime":122,"canonical":499,"series":500},"\u002Fithome-2025-day-17","Day 17：ImageMap Message  從互動海報到影片嵌入","在 Day 16 文章中，我們使用 Cloudflare Workers 實作了圖片代理功能。到目前為止，我們已經完成以下準備工作:","2025-09-30T11:58:32+08:00",[11,360,362,350],[11,362],4807,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10391164",{"name":366,"url":367,"day":170},{"path":502,"title":503,"description":504,"date":505,"updated":9,"tags":506,"categories":507,"draft":15,"wordCount":508,"readingTime":134,"canonical":509,"series":510},"\u002Fithome-2025-day-16","Day 16：Cloudflare Workers 圖片代理實作","在 Day 15 文章中，我們處理了 ImageMap Message 的背景圖，接著我們遇到了圖片不能出現副檔名及動態路徑支援不同解析度的問題。今天主要會透過 Cloudflare Workers 來解決這兩個問題，讓…","2025-09-29T16:15:41+08:00",[11,360,362,350],[11,362],3412,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10390567",{"name":366,"url":367,"day":181},{"path":512,"title":513,"description":514,"date":515,"updated":9,"tags":516,"categories":517,"draft":15,"wordCount":518,"readingTime":134,"canonical":519,"series":520},"\u002Fithome-2025-day-15","Day 15：共通屬性處理優化及 Imagemap  圖片製作","針對 Day 14 的程式碼架構進行優化。由於 Sender 和 Quick Reply 功能在所有回覆訊息類型中都能使用，我們應該將這些共用屬性抽取為獨立函數進行統一處理。","2025-09-28T21:03:38+08:00",[11,360,362,350],[11,362],4033,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10389697",{"name":366,"url":367,"day":192},{"path":522,"title":523,"description":524,"date":525,"updated":9,"tags":526,"categories":527,"draft":15,"wordCount":528,"readingTime":31,"canonical":529,"series":530},"\u002Fithome-2025-day-14","Day 14：LINE Bot Template Message 訊息回覆","經過前幾天的學習，我們已經成功掌握了 LINE Bot 六大基礎訊息類型的發送技巧，為訊息互動奠定了穩固的基礎。今天，我們將踏入更具挑戰性的進階應用領域！","2025-09-27T15:54:06+08:00",[11,360,362,350],[11,362],6372,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10388976",{"name":366,"url":367,"day":203},{"path":532,"title":533,"description":534,"date":535,"updated":9,"tags":536,"categories":537,"draft":15,"wordCount":538,"readingTime":122,"canonical":539,"series":540},"\u002Fithome-2025-day-13","Day 13：LINE Bot 客製化 Sender 與 Quick Reply 功能實作","LINE Bot 所有回覆訊息類型都具備「共用屬性」功能，這些屬性帶來兩項重要的互動體驗提升：","2025-09-26T11:41:34+08:00",[11,360,362,350],[11,362],4426,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10388037",{"name":366,"url":367,"day":214},{"path":542,"title":543,"description":544,"date":545,"updated":9,"tags":546,"categories":547,"draft":15,"wordCount":548,"readingTime":318,"canonical":549,"series":550},"\u002Fithome-2025-day-12","Day 12：LINE Bot Image、Video、Audio、Location 訊息回覆","Day 11 文章中，我們針對 LINE Bot 可以回覆的Text及Sticker基礎型別進行了封裝，不僅新增了 line-message.ts模組，還讓開發者可以用最少的參數產生 LINE Message 所需要的格…","2025-09-25T18:08:09+08:00",[11,360,362,350],[11,362],2977,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10387598",{"name":366,"url":367,"day":225},{"path":552,"title":553,"description":554,"date":555,"updated":9,"tags":556,"categories":557,"draft":15,"wordCount":558,"readingTime":31,"canonical":559,"series":560},"\u002Fithome-2025-day-11","Day 11：LINE Bot Text Emoji 與 Sticker 訊息回覆","目前我們的 LINE Bot 主要使用 Text 方式回覆訊息。今天將探討 Text 類型的 Emoji 應用，以及 Sticker 回覆方式，基於 Day 8 版本進行改寫。","2025-09-24T23:21:11+08:00",[11,360,350,362],[11,362],5659,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10386993",{"name":366,"url":367,"day":236},{"path":562,"title":563,"description":564,"date":565,"updated":9,"tags":566,"categories":567,"draft":15,"wordCount":568,"readingTime":318,"canonical":569,"series":570},"\u002Fithome-2025-day-10","Day 10：LINE Rich Menu Switch Action 提升使用者體驗","在 Day 9 文章中，我們結合 LINE 平台的功能，將天氣服務與圖片上傳服務整合，打造出第一張 LINE 圖文選單，透過 URI action 的方式觸發平台提供的互動效果。接著，我們使用客製化選單製作出 9 格的客…","2025-09-23T15:02:57+08:00",[11,360,362,350],[11,362],2906,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10386165",{"name":366,"url":367,"day":247},{"path":572,"title":573,"description":574,"date":575,"updated":9,"tags":576,"categories":577,"draft":15,"wordCount":578,"readingTime":318,"canonical":579,"series":580},"\u002Fithome-2025-day-09","Day  9：打造 LINE Rich Menu - 後台設計 vs API 客製化","在 Day8 文章中，我們透過整合雲端服務 Cloudinary，學習如何處理使用者上傳的圖片檔案，並將其儲存至雲端。然而，LINE Bot 除了讓使用者輸入文字回覆的方式之外，更常見的是透過圖文選單(Rich Menu…","2025-09-22T21:54:25+08:00",[11,360,362,350],[11,362],3285,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10385658",{"name":366,"url":367,"day":76},{"path":582,"title":583,"description":584,"date":585,"updated":9,"tags":586,"categories":587,"draft":15,"wordCount":588,"readingTime":17,"canonical":589,"series":590},"\u002Fithome-2025-day-08","Day 8：Cloudinary 雲端圖片儲存整合","在 Day 6 中，我們透過整合 OpenWeatherMap API 與座標位置訊息學習了如何結合第三方服務。今天將探索 Cloudinary 雲端服務，解決 LINE 圖片資源會過期的問題，學習如何透過 LINE M…","2025-09-21T23:13:19+08:00",[11,360,362,350],[11,362],7215,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10384968",{"name":366,"url":367,"day":110},{"path":592,"title":593,"description":594,"date":595,"updated":9,"tags":596,"categories":597,"draft":15,"wordCount":598,"readingTime":122,"canonical":599,"series":600},"\u002Fithome-2025-day-07","Day 7：Joi 環境變數統一驗證，重構 LINE Bot 天氣服務模組","在 Day 6 開發 LINE Bot 結合 OpenWeatherMap API 的過程中，我們採用私有方法將 API 請求處理與資料格式化整合在一起。今天將對 Day 6 的實作進行架構重構，主要目標是建立更完善的環…","2025-09-20T23:07:08+08:00",[11,360,362,350],[11,362],5157,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10384302",{"name":366,"url":367,"day":17},{"path":602,"title":603,"description":604,"date":605,"updated":9,"tags":606,"categories":607,"draft":15,"wordCount":608,"readingTime":134,"canonical":609,"series":610},"\u002Fithome-2025-day-06","Day 6：整合第三方 API 天氣查詢服務","Day 5 帶大家了解 LINE Bot 能接收使用者傳遞的「6+1」種訊息類型。之所以這樣強調，是因為 File 類型僅能在群組聊天中使用，這個限制我自己也經常忘記，所以習慣用「6+1」來提醒自己。","2025-09-19T21:07:47+08:00",[11,360,362,350],[11,362],3892,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10383636",{"name":366,"url":367,"day":31},{"path":612,"title":613,"description":614,"date":615,"updated":9,"tags":616,"categories":617,"draft":15,"wordCount":618,"readingTime":122,"canonical":619,"series":620},"\u002Fithome-2025-day-05","Day 5：整合 Pino Logger 提升 LINE Bot 專案的可維護性","看著專案逐漸成型，現在該開始重視日誌記錄的規劃了。在實際部署時，我們通常會區分 develop(開發環境)和 production(正式環境)兩種不同的執行環境，針對不同環境採用相應的日誌策略。","2025-09-18T23:30:00+08:00",[11,360,362,350],[11,362],4746,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10382298",{"name":366,"url":367,"day":122},{"path":622,"title":623,"description":624,"date":625,"updated":9,"tags":626,"categories":627,"draft":15,"wordCount":628,"readingTime":31,"canonical":629,"series":630},"\u002Fithome-2025-day-04","Day 4：掌握 LINE Bot 七種訊息類型與 NestJS 架構優化","目前我們都只使用 LINE Message Event 中的純文字(text)格式進行回覆，但除了純文字之外，LINE Bot 後端伺服器其實可以接收多種不同類型的訊息。今天就讓我們一起來深入了解這些訊息類型吧！","2025-09-17T22:53:37+08:00",[11,360,362,350],[11,362],5828,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10381651",{"name":366,"url":367,"day":134},{"path":632,"title":633,"description":634,"date":635,"updated":9,"tags":636,"categories":637,"draft":15,"wordCount":638,"readingTime":122,"canonical":639,"series":640},"\u002Fithome-2025-day-03","Day 3：Webhook 簽章驗證與訊息回覆策略(Push & Reply)","上一篇帶大家透過「Webhook 模式」成功架設了專屬的 LINE Bot 代理人。相信大家在體驗基礎功能後，對於 LINE Bot Webhook 還能監聽哪些事件、支援哪些類型的訊息回覆，以及如何確保後端收到的訊息確…","2025-09-16T21:53:39+08:00",[11,360,362,350],[11,362],5360,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10381303",{"name":366,"url":367,"day":318},{"path":642,"title":643,"description":644,"date":645,"updated":9,"tags":646,"categories":647,"draft":15,"wordCount":648,"readingTime":31,"canonical":649,"series":650},"\u002Fithome-2025-day-02","Day 2：從 Webhook 到後端，打造你的專屬機器人","上一篇，帶大家透過「Chat 模式」，讓自身變成客服機器人的方式。這篇會從「Webhook 模式」切入，並以 NestJS 作為後端框架，教你如何在休息時間，也能讓後端伺服器當你的替身幫你解惑使用者的問題。","2025-09-15T21:20:49+08:00",[11,360,362,350],[11,362],6590,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10380524",{"name":366,"url":367,"day":329},{"path":652,"title":653,"description":654,"date":655,"updated":9,"tags":656,"categories":657,"draft":15,"wordCount":658,"readingTime":318,"canonical":659,"series":660},"\u002Fithome-2025-day-01","Day 1：Hello World LINE Bot","每個程式語言的開始通常都會以練習 Hello World！作為一個簡單的起手式，LINE Bot 也不意外。這一系列會著重在 LINE Bot 的相關應用，帶大家用輕鬆的方式一起建立屬於自己的 Line Bot 聊天機器…","2025-09-14T22:48:33+08:00",[11,360,362,350],[11,362],2723,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10379895",{"name":366,"url":367,"day":340},{"path":662,"title":663,"description":664,"date":665,"updated":9,"tags":666,"categories":671,"draft":15,"wordCount":674,"readingTime":134,"canonical":9,"series":9},"\u002Fdbdiagram-tool","關聯式資料庫設計必備 - dbdiagram.io ERD 繪圖工具","還在煩惱如何設計關聯式資料表實體關聯圖嗎？ 使用 dbdiagram.io 加快你與同事之間的距離","2024-11-05T20:18:24+08:00",[667,668,669,670],"ERD","dbdiagram.io","DBML","資料庫設計",[672,673],"Database","開發工具",3982,{"path":676,"title":677,"description":678,"date":679,"updated":9,"tags":680,"categories":687,"draft":15,"wordCount":690,"readingTime":122,"canonical":9,"series":9},"\u002FPostgreSQL-1","前端勇士大闖六角後端體驗營 - 初探 PostgreSQL DML 語法","初步踏入後端的世界，了解何謂後端以及資料庫常見語法 DDL、DML。","2024-10-30T22:43:49+08:00",[681,682,683,684,685,686],"PostgreSQL","SQL","DML","DDL","資料庫","六角學院",[672,688,689],"後端實戰","學習心得",5220,{"path":692,"title":693,"description":694,"date":695,"updated":9,"tags":696,"categories":700,"draft":15,"wordCount":703,"readingTime":329,"canonical":9,"series":9},"\u002Fcss-flex-1","CSS flex 軸線對齊技巧 - 預設屬性","CSS flex 排版技巧你都了解了嗎？回歸學習初心的認識 flex 預設屬性","2024-10-24T20:29:08+08:00",[697,698,699],"Flexbox","前端排版","切版技巧",[701,702],"CSS","前端開發",1856,{"path":705,"title":706,"description":707,"date":708,"updated":9,"tags":709,"categories":712,"draft":15,"wordCount":714,"readingTime":329,"canonical":715,"series":716},"\u002Fithome-2024-day-30","Vue 3 用實作帶你看過核心概念 - Day 30：新手村的鐵人證書 - 完賽心得","花了整整半年左右的時間，每天下班都很用心的準備範例或是看書，這一段旅程對我來說真的很重要。擔心、害怕跟不安的心情一直充斥自己心中，擔心寫錯或是寫不好，想讓自己再多準備久一點再開始，所以拖到中秋連假才開始，想下定決心讓自己…","2024-10-13T12:42:25+08:00",[11,710,711],"2024 鐵人賽","Vue 3",[11,713],"Vue",1381,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10367206",{"name":717,"url":718,"day":22},"2024 iThome 鐵人賽：Vue 3 初學者：用實作帶你看過核心概念","https:\u002F\u002Fithelp.ithome.com.tw\u002Fusers\u002F20116554\u002Fironman\u002F7800",{"path":720,"title":721,"description":722,"date":723,"updated":9,"tags":724,"categories":727,"draft":15,"wordCount":728,"readingTime":134,"canonical":729,"series":730},"\u002Fithome-2024-day-29","Vue 3 用實作帶你看過核心概念 - Day 29：Composables(組合式函數)","Composables是 Vue 3 中的一個重要概念，它是利用 Vue 的 Composition API 來創建和管理可重用的有狀態邏輯的函數。Composables 允許我們將組件邏輯抽象成可重用的函數，使得代碼更…","2024-10-12T15:07:55+08:00",[11,710,711,725,726],"Options API","Composition API",[11,713],4233,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10366865",{"name":717,"url":718,"day":34},{"path":732,"title":733,"description":734,"date":735,"updated":9,"tags":736,"categories":738,"draft":15,"wordCount":739,"readingTime":134,"canonical":740,"series":741},"\u002Fithome-2024-day-28","Vue 3 用實作帶你看過核心概念 - Day 28：官方 Vue Router 的應用與技巧","路由設定方式，一般可以分成兩種：","2024-10-11T17:14:44+08:00",[11,710,711,725,737],"Vue Router",[11,713],4095,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10366520",{"name":717,"url":718,"day":45},{"path":743,"title":744,"description":745,"date":746,"updated":9,"tags":747,"categories":748,"draft":15,"wordCount":749,"readingTime":122,"canonical":750,"series":751},"\u002Fithome-2024-day-27","Vue 3 用實作帶你看過核心概念 - Day 27：VeeValidate 表單驗證工具","在開發 Vue 應用程式時，表單驗證至關重要，它能確保使用者輸入的資料符合預期的格式和要求。今天來介紹一款專門用於 Vue 的表單驗證工具—VeeValidate v4。這個工具不僅能幫助開發者輕鬆實現表單驗證，還提供了…","2024-10-10T21:02:16+08:00",[11,710,711,725],[11,713],4461,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10366165",{"name":717,"url":718,"day":56},{"path":753,"title":754,"description":755,"date":756,"updated":9,"tags":757,"categories":758,"draft":15,"wordCount":759,"readingTime":318,"canonical":760,"series":761},"\u002Fithome-2024-day-26","Vue 3 用實作帶你看過核心概念 - Day 26：KeepAlive 與 Teleport 內置組件","預設情況下，切換組件會導致組件的創建及銷毀，無法保持組件內部的狀態。","2024-10-09T18:50:53+08:00",[11,710,711,725],[11,713],3158,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10365724",{"name":717,"url":718,"day":67},{"path":763,"title":764,"description":765,"date":766,"updated":9,"tags":767,"categories":768,"draft":15,"wordCount":769,"readingTime":318,"canonical":770,"series":771},"\u002Fithome-2024-day-25","Vue 3 用實作帶你看過核心概念 - Day 25：自定義指令(Custom Directives)","Vue不僅提供了豐富的內置指令用於操作DOM元素，還允許開發者創建自定義指令。透過自定義指令，我們可以對DOM元素進行更細緻的控制，並在指令的不同生命週期階段執行特定的邏輯，從而實現更靈活的功能擴展。","2024-10-08T22:05:32+08:00",[11,710,711,725],[11,713],3116,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10365355",{"name":717,"url":718,"day":79},{"path":773,"title":774,"description":775,"date":776,"updated":9,"tags":777,"categories":778,"draft":15,"wordCount":779,"readingTime":329,"canonical":780,"series":781},"\u002Fithome-2024-day-24","Vue 3 用實作帶你看過核心概念 - Day 24：異步加載(Lazy loading)","在大型項目中，我們通常需要將應用拆分為更小的代碼模塊，並僅在需要時才從服務器加載相關組件，以減少初次加載的資源量。Vue 提供了 defineAsyncComponent 方法來實現組件的異步加載，這樣可以有效提高應用的…","2024-10-07T20:28:27+08:00",[11,710,711,725],[11,713],2171,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10364861",{"name":717,"url":718,"day":90},{"path":783,"title":784,"description":785,"date":786,"updated":9,"tags":787,"categories":788,"draft":15,"wordCount":789,"readingTime":318,"canonical":790,"series":791},"\u002Fithome-2024-day-23","Vue 3 用實作帶你看過核心概念 - Day 23：依賴注入( Provide-Inject )","在Dayxx中提到過，父子組件之間的數據傳遞可以通過props來實現。然而，當祖孫層組件需要進行數據傳遞時，中間層級的組件可能並不需要這個props，但卻不得不為了使子組件獲取數據而被迫傳遞。","2024-10-06T15:14:51+08:00",[11,710,711,725],[11,713],3183,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10364252",{"name":717,"url":718,"day":101},{"path":793,"title":794,"description":795,"date":796,"updated":9,"tags":797,"categories":798,"draft":15,"wordCount":799,"readingTime":134,"canonical":800,"series":801},"\u002Fithome-2024-day-22","Vue 3 用實作帶你看過核心概念 - Day 22：v-slot 插槽使用","先前Day 18中提到父組件可以通過props將參數資料傳遞給子組件進行渲染，這樣可以有效地將資料處理與畫面渲染的工作分開。然而，當我們需要更加客製化的呈現內容，由父組件來控制子組件的部分顯示時，可以使用v-slot 指…","2024-10-05T12:32:51+08:00",[11,710,711,725],[11,713],4292,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10363713",{"name":717,"url":718,"day":113},{"path":803,"title":804,"description":805,"date":806,"updated":9,"tags":807,"categories":808,"draft":15,"wordCount":809,"readingTime":329,"canonical":810,"series":811},"\u002Fithome-2024-day-21","Vue 3 用實作帶你看過核心概念 - Day 21： 組件透傳屬性(Attributes)的應用","當父組件向子組件傳遞屬性或監聽器，而這些屬性未在子組件中定義為props或emits時，它們會自動繼承並附加到子組件的根元素上，常見的屬性包括class、style、id等。這些屬性可以透過$attrs屬性訪問並進行操作…","2024-10-04T22:42:54+08:00",[11,710,711,725],[11,713],2146,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10363469",{"name":717,"url":718,"day":125},{"path":813,"title":814,"description":815,"date":816,"updated":9,"tags":817,"categories":818,"draft":15,"wordCount":819,"readingTime":122,"canonical":820,"series":821},"\u002Fithome-2024-day-20","Vue 3 用實作帶你看過核心概念 - Day 20：組件使用 v-model 雙向綁定","在Day 13中，我們介紹了表單元素（例如輸入框）如何處理數據雙向綁定。當需要將表單元素與一個響應式變數綁定時，v-model提供雙向綁定功能。這代表當畫面上表單元素的變動會即時影響Vue數據，同時當Vue數據的值改變時…","2024-10-03T23:40:48+08:00",[11,710,711,725],[11,713],5191,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10362957",{"name":717,"url":718,"day":137},{"path":823,"title":824,"description":825,"date":826,"updated":9,"tags":827,"categories":828,"draft":15,"wordCount":829,"readingTime":318,"canonical":830,"series":831},"\u002Fithome-2024-day-19","Vue 3 用實作帶你看過核心概念 - Day 19：子組件向父組件發射事件 - emits","組件可以通過$emit(functionName, params)自定義事件名稱並傳遞參數。自定義事件名稱建議使用kebab-case來命名自定義事件名稱，以確保命名風格與HTML 屬性一致性。此外，自定義事件還支持事件…","2024-10-02T15:51:16+08:00",[11,710,711,725],[11,713],2877,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10362144",{"name":717,"url":718,"day":148},{"path":833,"title":834,"description":835,"date":836,"updated":9,"tags":837,"categories":838,"draft":15,"wordCount":839,"readingTime":31,"canonical":840,"series":841},"\u002Fithome-2024-day-18","Vue 3 用實作帶你看過核心概念 - Day 18：父組件向子組件傳值 - props","組件之間的傳值必須透過聲明 props 的方式，這樣可以避免與HTML的屬性(attribute)混淆。父組件傳遞參數給子組件的方式有以下兩種方式：","2024-10-01T22:28:48+08:00",[11,710,711,725],[11,713],5782,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10361721",{"name":717,"url":718,"day":159},{"path":843,"title":844,"description":845,"date":846,"updated":9,"tags":847,"categories":848,"draft":15,"wordCount":849,"readingTime":318,"canonical":850,"series":851},"\u002Fithome-2024-day-17","Vue 3 用實作帶你看過核心概念 - Day 17：組件基礎 - 全局註冊與區域註冊","在 Day 5 我們提到可以將應用拆分為根組件和多個組件實例，並將功能模塊化。","2024-09-30T23:30:10+08:00",[11,710,711,725],[11,713],2954,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10361253",{"name":717,"url":718,"day":170},{"path":853,"title":854,"description":855,"date":856,"updated":9,"tags":857,"categories":858,"draft":15,"wordCount":859,"readingTime":122,"canonical":860,"series":861},"\u002Fithome-2024-day-16","Vue 3 用實作帶你看過核心概念 - Day 16：使用 ref 屬性引用模板元素","雖然 Vue 透過模板幫助我們處理了大部分的DOM 操作，但在某些情況下，仍然需要手動操作 DOM。例如，在使用第三方套件（如 Bootstrap 的 Modal）時，或者需要調用像video.play()和video.…","2024-09-29T16:25:45+08:00",[11,710,711,725],[11,713],4608,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10360419",{"name":717,"url":718,"day":181},{"path":863,"title":864,"description":865,"date":866,"updated":9,"tags":867,"categories":868,"draft":15,"wordCount":488,"readingTime":122,"canonical":869,"series":870},"\u002Fithome-2024-day-15","Vue 3 用實作帶你看過核心概念 - Day 15：監聽器(Watchers)","在響應式狀態變化時執行特定操作，需要使用watch 監聽器。這些操作可能包含副作用 (side effects)，如發送請求、調用 API，或更新 DOM 以外的系統狀態，亦或是處理自定義的邏輯。","2024-09-28T18:30:31+08:00",[11,710,711,725],[11,713],"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10359958",{"name":717,"url":718,"day":192},{"path":872,"title":873,"description":874,"date":875,"updated":9,"tags":876,"categories":877,"draft":15,"wordCount":878,"readingTime":134,"canonical":879,"series":880},"\u002Fithome-2024-day-14","Vue 3 用實作帶你看過核心概念 - Day 14：生命週期鉤子(Lifecycle Hooks)","在 Vue 中，當一個組件創建時，它會經歷一系列的流程，這些流程決定了組件從初始化到渲染，再到最終銷毀的過程。","2024-09-27T21:57:32+08:00",[11,710,711,725],[11,713],3780,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10359419",{"name":717,"url":718,"day":203},{"path":882,"title":883,"description":884,"date":885,"updated":9,"tags":886,"categories":887,"draft":15,"wordCount":888,"readingTime":318,"canonical":889,"series":890},"\u002Fithome-2024-day-13","Vue 3 用實作帶你看過核心概念 - Day 13：v-model 雙向綁定控制 - 常用於表單輸入","表單輸入是開發中非常常見的需求，原始方式通常需要手動使用v-bind綁定表單元素的值 (value)，並透過v-on綁定input事件來監聽輸入變化。","2024-09-26T21:49:25+08:00",[11,710,711,725],[11,713],3153,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10358850",{"name":717,"url":718,"day":214},{"path":892,"title":893,"description":894,"date":895,"updated":9,"tags":896,"categories":897,"draft":15,"wordCount":898,"readingTime":134,"canonical":899,"series":900},"\u002Fithome-2024-day-12","Vue 3 用實作帶你看過核心概念 - Day 12：v-on 指令 - 事件處理","在 Vue 中，監聽 HTML DOM 元素的事件變化，可以使用v-on 指令將 JavaScript 事件處理器綁定到對應的DOM 事件上。這個指令的縮寫符號為@，例如：v-on:click，其縮寫方式為@click。","2024-09-25T21:42:59+08:00",[11,710,711,725],[11,713],3808,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10358241",{"name":717,"url":718,"day":225},{"path":902,"title":903,"description":904,"date":905,"updated":9,"tags":906,"categories":907,"draft":15,"wordCount":908,"readingTime":134,"canonical":909,"series":910},"\u002Fithome-2024-day-11","Vue 3 用實作帶你看過核心概念 - Day 11：v-for 指令的基本與進階應用","當數據類型是陣列或物件時，我們不會希望將重複的選項或元素直接硬編碼在模板中。這樣的寫法會導致代碼冗長且不具可維護性。","2024-09-24T23:11:25+08:00",[11,710,711,725],[11,713],4381,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10357705",{"name":717,"url":718,"day":236},{"path":912,"title":913,"description":914,"date":915,"updated":9,"tags":916,"categories":917,"draft":15,"wordCount":918,"readingTime":318,"canonical":919,"series":920},"\u002Fithome-2024-day-10","Vue 3 用實作帶你看過核心概念 - Day 10：條件渲染 - v-if 與 v-show 的區別與應用","開發中遇到需要處理【如果是...就要...】的情境時，Vue 提供了 v-if 指令來幫助我們根據條件進行元素的渲染。這樣可以在特定條件滿足時動態地顯示或隱藏某些元素。","2024-09-23T23:39:24+08:00",[11,710,711,725],[11,713],2827,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10357160",{"name":717,"url":718,"day":247},{"path":922,"title":923,"description":924,"date":925,"updated":9,"tags":926,"categories":927,"draft":15,"wordCount":928,"readingTime":122,"canonical":929,"series":930},"\u002Fithome-2024-day-09","Vue 3 用實作帶你看過核心概念 - Day 9：Class 與 Style 的樣式綁定","v-bind 指令通常用於綁定 HTML 屬性，但在實際開發中，最常見的應用場景之一還是綁定class和 style這兩個 HTML 屬性。","2024-09-22T15:05:53+08:00",[11,710,711,725],[11,713],4630,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10356119",{"name":717,"url":718,"day":76},{"path":932,"title":933,"description":934,"date":935,"updated":9,"tags":936,"categories":937,"draft":15,"wordCount":938,"readingTime":134,"canonical":939,"series":940},"\u002Fithome-2024-day-08","Vue 3 用實作帶你看過核心概念 - Day 8：計算屬性應用與實踐","在 Day 6 在使用 Vue 的Mustache語法時，可以用來放置表達式。不過，這邊建議避免在 Mustache 中撰寫過於複雜的邏輯。這樣的建議主要有兩個原因：","2024-09-21T21:33:29+08:00",[11,710,711,725],[11,713],4060,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10355474",{"name":717,"url":718,"day":110},{"path":942,"title":943,"description":944,"date":945,"updated":9,"tags":946,"categories":947,"draft":15,"wordCount":948,"readingTime":122,"canonical":949,"series":950},"\u002Fithome-2024-day-07","Vue 3 用實作帶你看過核心概念 - Day 7： 響應式基礎 - Options API","前面提到了模板搭配指令及 Mustache 的用法。今天則是要介紹所謂透過getter跟setter取值跟賦值的方式在 JavaScript 是怎麼做到的，這部分會跟 Vue 本身的響應式基礎有很大相關。此外，我也會帶著…","2024-09-20T23:41:42+08:00",[11,710,711],[11,713],4407,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10354781",{"name":717,"url":718,"day":17},{"path":952,"title":953,"description":954,"date":955,"updated":9,"tags":956,"categories":957,"draft":15,"wordCount":958,"readingTime":134,"canonical":959,"series":960},"\u002Fithome-2024-day-06","Vue 3 用實作帶你看過核心概念 - Day 6：數據綁定和模板(Template)","Vue 使用基於 HTML 的模板語法（Template Syntax），將 Vue 實例中的數據綁定到模板中進行顯示。根據綁定的類型不同，數據可以影響元素的內容、屬性或樣式。","2024-09-19T20:39:46+08:00",[11,710,711,725],[11,713],3402,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10354231",{"name":717,"url":718,"day":31},{"path":962,"title":963,"description":964,"date":965,"updated":9,"tags":966,"categories":967,"draft":15,"wordCount":968,"readingTime":318,"canonical":969,"series":970},"\u002Fithome-2024-day-05","Vue 3 用實作帶你看過核心概念 - Day 5：Options API vs Composition API","前面已經詳細說明了 Vue 的環境建置方式，接下來將逐步介紹 Vue 應用說明，並比較Options API與Composition API的撰寫風格。","2024-09-18T22:10:36+08:00",[11,710,711,725,726],[11,713],2902,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10353717",{"name":717,"url":718,"day":122},{"path":972,"title":973,"description":974,"date":975,"updated":9,"tags":976,"categories":977,"draft":15,"wordCount":658,"readingTime":318,"canonical":978,"series":979},"\u002Fithome-2024-day-04","Vue 3 用實作帶你看過核心概念 - Day 4：基於 Vite 建構工具的 Vue 專案結構解析","在 Day 3 的教學中，學習了如何使用 Vue 鷹架工具(Vue project scaffolding tool)來生成一個基於 Vite 環境的專案。今天，我將更進一步地解析這個專案的資料夾結構，幫助大家更好地理解…","2024-09-17T23:27:07+08:00",[11,710,711,725],[11,713],"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10352470",{"name":717,"url":718,"day":134},{"path":981,"title":982,"description":983,"date":984,"updated":9,"tags":985,"categories":986,"draft":15,"wordCount":987,"readingTime":329,"canonical":988,"series":989},"\u002Fithome-2024-day-03","Vue 3 用實作帶你看過核心概念 - Day 3：使用 Vite 建構工具搭建 Vue 專案","⭐ 需要特別注意，需要事先安裝Nodejs。若不確定是否已安裝 Nodejs 也可以開啟終端機，執行以下指令確認版本。","2024-09-16T23:29:45+08:00",[11,710,711,725],[11,713],2100,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10351398",{"name":717,"url":718,"day":318},{"path":991,"title":992,"description":993,"date":994,"updated":9,"tags":995,"categories":996,"draft":15,"wordCount":997,"readingTime":329,"canonical":998,"series":999},"\u002Fithome-2024-day-02","Vue 3 用實作帶你看過核心概念 - Day 2：命令式編程 vs 聲明式編程","還記得我們在使用純 HTML 和 JavaScript 時，如何實現按下按鈕來變更文字顏色嗎？讓我們一起回想一下什麼是命令式宣告。","2024-09-15T22:52:27+08:00",[11,710,711,725,726],[11,713],1881,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10350459",{"name":717,"url":718,"day":329},{"path":1001,"title":1002,"description":1003,"date":1004,"updated":9,"tags":1005,"categories":1006,"draft":15,"wordCount":1007,"readingTime":340,"canonical":1008,"series":1009},"\u002Fithome-2024-day-01","Vue 3 用實作帶你看過核心概念 - Day 1：前言介紹","大家好，我是 Antonio(安東尼奧)，目前是一名 Angular 的新手工程師，同時，也是一名熱愛寫程式的工程師。去年參加六角學院的 Vue 直播班，在那時候就深深著迷著 Vue 的語言，自此這半年多的時間裡，我白天…","2024-09-14T17:32:19+08:00",[11,710,711],[11,713],988,"https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10350457",{"name":717,"url":718,"day":340},{"path":1011,"title":1012,"description":1013,"date":1014,"updated":9,"tags":1015,"categories":1017,"draft":15,"wordCount":1019,"readingTime":329,"canonical":9,"series":9},"\u002Fhexschool-experience","六角學院 - 軟體工程師體驗營","這麼多線上課程? 你不想知道什麼是最吸引我的線上學習課程嗎?","2024-05-31T21:40:05+08:00",[686,1016],"軟體工程師體驗營",[689,1018],"前端成長記",1109,{"path":1021,"title":1022,"description":1023,"date":1024,"updated":9,"tags":1025,"categories":1033,"draft":15,"wordCount":1035,"readingTime":318,"canonical":9,"series":9},"\u002FJS-10","JavaScript：var、let、const之間的差異解析","var、let及const是JavaScript中宣告變數的關鍵字，它們在作用域、對於for迴圈的影響、提升 (Hoisting) 的差異及重複宣告的處理上有所不同。","2023-12-10T23:53:30+08:00",[1026,1027,1028,1029,1030,1031,1032],"ES6","var","let","const","Hoisting","Scope","TDZ",[1034,702],"JavaScript",2873,{"path":1037,"title":1038,"description":1039,"date":1040,"updated":9,"tags":1041,"categories":1048,"draft":15,"wordCount":1049,"readingTime":122,"canonical":9,"series":9},"\u002FJS-9","JavaScript：陣列的常見操作方法","掌握 JavaScript 陣列操作！從forEach、map、filter、findIndex、reduce、sort，深入了解這些方法，使你的程式碼更具靈活性和效率！","2023-12-01T15:01:06+08:00",[1042,1043,1044,1045,1046,1047],"forEach","map","filter","reduce","sort","findIndex",[1034,702],4846,{"path":1051,"title":1052,"description":1053,"date":1054,"updated":9,"tags":1055,"categories":1060,"draft":15,"wordCount":1061,"readingTime":318,"canonical":9,"series":9},"\u002FJS-8","JavaScript：ES module 匯入與匯出","使用\u003C script >標籤讓瀏覽器中的網頁能夠使用 ES 模組功能時，你了解不同的匯入及匯出方法了嗎？","2023-11-30T15:28:23+08:00",[1026,1056,1057,1058,1059],"ES Module","CommonJS","Node.js","模組化開發",[1034,702],2913,{"path":1063,"title":1064,"description":1065,"date":1066,"updated":9,"tags":1067,"categories":1070,"draft":15,"wordCount":1072,"readingTime":134,"canonical":9,"series":9},"\u002FReact-2","React：JSX 是什麼？為何在 React 中使用 JSX？","透過 JSX 語法糖，你能夠在一次 JavaScript 撰寫中包含 HTML 與 CSS 的內容","2023-11-29T16:03:40+08:00",[1068,1034,1069],"JSX","Babel",[1071,702],"React",3595,{"path":1074,"title":1075,"description":1076,"date":1077,"updated":9,"tags":1078,"categories":1081,"draft":15,"wordCount":1082,"readingTime":329,"canonical":9,"series":9},"\u002FReact-1","React：Pure Function 的概念及其在 React 中的應用","探索 Pure Function 概念及其與 React 的相互關係。","2023-11-29T15:50:17+08:00",[1034,1079,1080],"Pure Function","Functional Programming",[1071],1368,{"path":1084,"title":1085,"description":1086,"date":1087,"updated":9,"tags":1088,"categories":1093,"draft":15,"wordCount":1094,"readingTime":122,"canonical":9,"series":9},"\u002FJS-6","JavaScript：深入理解Promise的原理及實際應用","透過Promise，我們能夠有效解決JavaScript中的異步事件，使得程式碼更為清晰和可讀。","2023-11-29T14:49:18+08:00",[1089,1090,1091,1092],"Promise","AsyncAwait","Asynchronous Programming","異步處理",[1034,702],5479,{"path":1096,"title":1097,"description":1098,"date":1099,"updated":9,"tags":1100,"categories":1105,"draft":15,"wordCount":1106,"readingTime":122,"canonical":9,"series":9},"\u002FJS-5","JavaScript：物件傳參考特性(Pass by Reference)","淺拷貝(shallow copy)與深拷貝(deep copy)在JavaScript中的應用與理解","2023-11-29T09:55:50+08:00",[1101,1102,1103,1104],"Pass by Reference","Shallow Copy","Deep Copy","傳值與傳參考",[1034,702],4544,{"path":1108,"title":1109,"description":1110,"date":1111,"updated":9,"tags":1112,"categories":1118,"draft":15,"wordCount":1120,"readingTime":329,"canonical":9,"series":9},"\u002FJS-4","JavaScript：注重關注點的分離","透過關注點分離的設計方式，可顯著提高系統整體的可維護性。","2023-11-29T09:44:29+08:00",[1113,1114,1115,1116,1117],"SoC","MVC","Design Patterns","Clean Code","Refactoring",[1034,1119],"Software Engineering",1977,{"path":1122,"title":1123,"description":1124,"date":1125,"updated":9,"tags":1126,"categories":1132,"draft":15,"wordCount":1133,"readingTime":329,"canonical":9,"series":9},"\u002FJS-3","JavaScript：掌握箭頭函式，優雅簡約的程式寫作","深入解析ES6箭頭函數：揭開與傳統函式的差異。","2023-11-29T01:02:36+08:00",[1127,1128,1129,1130,1131],"Arrow Function","this","Lexical Scoping","Syntactic Sugar","Callback Function",[1034,702],2142,{"path":1135,"title":1136,"description":1137,"date":1138,"updated":9,"tags":1139,"categories":1143,"draft":15,"wordCount":1144,"readingTime":329,"canonical":9,"series":9},"\u002FJS-2","JavaScript：深入了解This的指向與應用","探索JavaScript This 的指向：深入剖析判斷的技巧。","2023-11-28T22:22:45+08:00",[1128,1140,1131,1141,1142],"Execution Context","Binding","Fundamentals",[1034,702],1963,{"path":1146,"title":1147,"description":1148,"date":1149,"updated":9,"tags":1150,"categories":1154,"draft":15,"wordCount":1155,"readingTime":340,"canonical":9,"series":9},"\u002FJS-1","JavaScript：淺談ES6常見縮寫","JavaScript ES6縮寫技巧：輕鬆簡化程式碼，提升效率！。","2023-11-28T13:38:14+08:00",[1026,1151,1152,1153],"Shorthand","Spread Operator","Object",[1034,702],818,{"path":1157,"title":1158,"description":1159,"date":1160,"updated":9,"tags":1161,"categories":1165,"draft":15,"wordCount":1166,"readingTime":340,"canonical":9,"series":9},"\u002FEmmet-1","前端開發神器：使用Emmet提升網頁開發效率","本文將介紹如何利用Emmet來大幅提高前端開發效率，讓你的編碼速度如專家般飛快。","2023-10-31T14:40:54+08:00",[1162,1163,1164],"Emmet","VSCode","HTML",[702,673],865,{"path":1168,"title":1169,"description":1170,"date":1171,"updated":9,"tags":1172,"categories":1177,"draft":15,"wordCount":1179,"readingTime":340,"canonical":9,"series":9},"\u002Fhexo-github-4","建立自己的部落格：了解Hexo指令，更換next部落格主題","今天的你跟我都是Hexo指令指揮官，讓我們將部落格造型大改造一下吧!!!","2023-10-20T14:33:38+08:00",[1173,1174,1175,1176],"Hexo","NexT","git clone","Hexo指令",[1178],"Blog",979,{"path":1181,"title":1182,"description":1183,"date":1184,"updated":9,"tags":1185,"categories":1189,"draft":15,"wordCount":1190,"readingTime":329,"canonical":9,"series":9},"\u002Fhexo-github-3","建立自己的部落格：修改Hexo設定檔中Site，查看其變化","今天的你跟我都是部落格工程師，我們一起來將網頁做一些小小的改變，有一天匯集在一起就會讓你的部落格變的與眾不同。","2023-10-18T20:50:31+08:00",[1173,1163,1186,1187,1188],"Sublime Text","YAML","SEO",[1178],1798,{"path":1192,"title":1193,"description":1194,"date":1195,"updated":9,"tags":1196,"categories":1199,"draft":15,"wordCount":1200,"readingTime":340,"canonical":9,"series":9},"\u002Fhexo-github-2","建立自己的部落格：創建Hexo Blog初始的模板","踏出那關鍵的第一步，從白紙到完整的部落格，一同見證你的部落格誕生的奇妙時刻。","2023-10-17T15:59:37+08:00",[1173,1197,1198],"Hexo-cli","hexo init",[1178],941,{"path":1202,"title":1203,"description":1204,"date":1205,"updated":9,"tags":1206,"categories":1208,"draft":15,"wordCount":1209,"readingTime":340,"canonical":9,"series":9},"\u002Fhexo-github-1","建立自己的部落格：認識Hexo及所其需工具(Nodejs & Git)","打造屬於自己風格的部落格其實不難，讓我們一步步手把手教你如何實現這個目標。","2023-10-16T08:30:27+08:00",[1173,1058,1207],"Git",[1178],790,{"id":1211,"title":6,"body":1212,"canonical":18,"categories":3145,"date":8,"description":7,"draft":15,"extension":3146,"meta":3147,"navigation":1300,"ogImage":9,"path":5,"rawbody":3148,"readingTime":17,"robots":9,"schemaOrg":9,"seo":3149,"series":3150,"sitemap":3151,"slug":3155,"stem":3156,"tags":3157,"updated":9,"wordCount":16,"__hash__":3158},"posts\u002F2026-10-14-ithome-2026-day-30.md",{"type":1213,"value":1214,"toc":3133},"minimark",[1215,1224,1230,1237,1244,1249,1260,1265,1460,1473,1480,1485,1675,1680,1732,1735,1740,1743,1748,1929,1942,1945,1988,1994,2001,2110,2124,2215,2218,2223,2286,2289,2294,2443,2461,2464,2467,2470,2478,2481,2487,2490,2496,2507,2510,2516,2528,2538,2544,2550,2557,2560,2565,2572,2576,2719,2722,2725,2728,2733,2744,2747,2753,2762,2765,2771,2777,2780,2848,2858,2864,2868,2877,2883,2889,2911,2930,2944,2947,2958,2962,2967,2976,3010,3016,3019,3056,3059,3062,3065,3069,3072,3075,3078,3093,3096,3099,3105,3108,3111,3120,3123,3126,3129],[1216,1217,1218,1219,1223],"p",{},"平常在 Angular 中，我們可以透過 ",[1220,1221,1222],"code",{},"providers"," 決定 Service 的注入範圍。例如註冊在 Root，讓整個 Application 共用同一個實例；或註冊在 Component，讓 Service 隨著 Component 一起建立與銷毀。",[1216,1225,1226,1227,1229],{},"除了這兩種方式，Angular Router 也允許我們在 Route 中宣告 ",[1220,1228,1222],{},"，讓特定路由及其子路由使用專屬的 Service。",[1216,1231,1232,1233],{},"不過，這裡有個容易忽略的問題：",[1234,1235,1236],"strong",{},"當使用者離開路由時，註冊在 Route Providers 的 Service，也會跟著銷毀嗎？",[1216,1238,1239,1240,1243],{},"今天就透過一個簡單的範例觀察這個行為，再介紹 Angular 22.2 正式提供的 ",[1220,1241,1242],{},"withAutoCleanupInjectors()","。",[1245,1246,1248],"h2",{"id":1247},"route-providers-的生命週期","Route Providers 的生命週期",[1216,1250,1251,1252,1255,1256,1259],{},"首先建立一個 ",[1220,1253,1254],{},"CounterService","，透過 ",[1220,1257,1258],{},"OnDestroy"," 觀察 Service 什麼時候被銷毀。",[1216,1261,1262],{},[1220,1263,1264],{},"counter\u002Fcounter.service.ts",[1266,1267,1272],"pre",{"className":1268,"code":1269,"language":1270,"meta":1271,"style":1271},"language-ts shiki shiki-themes github-light github-dark-dimmed","import { Injectable, OnDestroy } from '@angular\u002Fcore';\n\nlet nextId = 0;\n\n@Injectable()\nexport class CounterService implements OnDestroy {\n  readonly id = ++nextId;\n\n  constructor() {\n    console.log(`CounterService #${this.id} created`);\n  }\n\n  ngOnDestroy() {\n    console.log(`CounterService #${this.id} destroyed`);\n  }\n}\n","ts","",[1220,1273,1274,1296,1302,1318,1322,1334,1356,1374,1378,1386,1414,1419,1423,1430,1451,1455],{"__ignoreMap":1271},[1275,1276,1278,1282,1286,1289,1293],"span",{"class":1277,"line":340},"line",[1275,1279,1281],{"class":1280},"s7YZ4","import",[1275,1283,1285],{"class":1284},"sYgZi"," { Injectable, OnDestroy } ",[1275,1287,1288],{"class":1280},"from",[1275,1290,1292],{"class":1291},"s-HuK"," '@angular\u002Fcore'",[1275,1294,1295],{"class":1284},";\n",[1275,1297,1298],{"class":1277,"line":329},[1275,1299,1301],{"emptyLinePlaceholder":1300},true,"\n",[1275,1303,1304,1306,1309,1312,1316],{"class":1277,"line":318},[1275,1305,1028],{"class":1280},[1275,1307,1308],{"class":1284}," nextId ",[1275,1310,1311],{"class":1280},"=",[1275,1313,1315],{"class":1314},"sviXB"," 0",[1275,1317,1295],{"class":1284},[1275,1319,1320],{"class":1277,"line":134},[1275,1321,1301],{"emptyLinePlaceholder":1300},[1275,1323,1324,1327,1331],{"class":1277,"line":122},[1275,1325,1326],{"class":1284},"@",[1275,1328,1330],{"class":1329},"sPO5f","Injectable",[1275,1332,1333],{"class":1284},"()\n",[1275,1335,1336,1339,1342,1346,1349,1353],{"class":1277,"line":31},[1275,1337,1338],{"class":1280},"export",[1275,1340,1341],{"class":1280}," class",[1275,1343,1345],{"class":1344},"sOLd2"," CounterService",[1275,1347,1348],{"class":1280}," implements",[1275,1350,1352],{"class":1351},"sMOND"," OnDestroy",[1275,1354,1355],{"class":1284}," {\n",[1275,1357,1358,1361,1365,1368,1371],{"class":1277,"line":17},[1275,1359,1360],{"class":1280},"  readonly",[1275,1362,1364],{"class":1363},"stnAF"," id",[1275,1366,1367],{"class":1280}," =",[1275,1369,1370],{"class":1280}," ++",[1275,1372,1373],{"class":1284},"nextId;\n",[1275,1375,1376],{"class":1277,"line":110},[1275,1377,1301],{"emptyLinePlaceholder":1300},[1275,1379,1380,1383],{"class":1277,"line":76},[1275,1381,1382],{"class":1280},"  constructor",[1275,1384,1385],{"class":1284},"() {\n",[1275,1387,1388,1391,1394,1397,1400,1402,1405,1408,1411],{"class":1277,"line":247},[1275,1389,1390],{"class":1284},"    console.",[1275,1392,1393],{"class":1329},"log",[1275,1395,1396],{"class":1284},"(",[1275,1398,1399],{"class":1291},"`CounterService #${",[1275,1401,1128],{"class":1314},[1275,1403,1404],{"class":1291},".",[1275,1406,1407],{"class":1284},"id",[1275,1409,1410],{"class":1291},"} created`",[1275,1412,1413],{"class":1284},");\n",[1275,1415,1416],{"class":1277,"line":236},[1275,1417,1418],{"class":1284},"  }\n",[1275,1420,1421],{"class":1277,"line":225},[1275,1422,1301],{"emptyLinePlaceholder":1300},[1275,1424,1425,1428],{"class":1277,"line":214},[1275,1426,1427],{"class":1329},"  ngOnDestroy",[1275,1429,1385],{"class":1284},[1275,1431,1432,1434,1436,1438,1440,1442,1444,1446,1449],{"class":1277,"line":203},[1275,1433,1390],{"class":1284},[1275,1435,1393],{"class":1329},[1275,1437,1396],{"class":1284},[1275,1439,1399],{"class":1291},[1275,1441,1128],{"class":1314},[1275,1443,1404],{"class":1291},[1275,1445,1407],{"class":1284},[1275,1447,1448],{"class":1291},"} destroyed`",[1275,1450,1413],{"class":1284},[1275,1452,1453],{"class":1277,"line":192},[1275,1454,1418],{"class":1284},[1275,1456,1457],{"class":1277,"line":181},[1275,1458,1459],{"class":1284},"}\n",[1216,1461,1462,1463,1466,1467,1469,1470,1472],{},"這裡用 ",[1220,1464,1465],{},"nextId"," 記錄 Service 建立的次數，每次建立新實例時，",[1220,1468,1407],{}," 就會增加 1。即使 Service 被銷毀，",[1220,1471,1465],{}," 也不會重設，方便區分不同的實例。",[1216,1474,1475,1476,1479],{},"接著建立 Counter 頁面，注入剛才的 Service，並使用 ",[1220,1477,1478],{},"input()"," 接收路由參數。",[1216,1481,1482],{},[1220,1483,1484],{},"counter\u002Fcounter.component.ts",[1266,1486,1488],{"className":1268,"code":1487,"language":1270,"meta":1271,"style":1271},"import { Component, inject, input, OnDestroy } from '@angular\u002Fcore';\nimport { CounterService } from '.\u002Fcounter.service';\n\n@Component({\n  selector: 'app-counter',\n  templateUrl: '.\u002Fcounter.component.html',\n  styleUrl: '.\u002Fcounter.component.css',\n})\nexport class CounterComponent implements OnDestroy {\n  readonly id = input\u003Cstring>();\n  readonly counterService = inject(CounterService);\n\n  constructor() {\n    console.log('CounterComponent created');\n  }\n\n  ngOnDestroy() {\n    console.log('CounterComponent destroyed');\n  }\n}\n",[1220,1489,1490,1503,1517,1521,1531,1542,1552,1562,1567,1582,1602,1617,1621,1627,1640,1644,1648,1654,1667,1671],{"__ignoreMap":1271},[1275,1491,1492,1494,1497,1499,1501],{"class":1277,"line":340},[1275,1493,1281],{"class":1280},[1275,1495,1496],{"class":1284}," { Component, inject, input, OnDestroy } ",[1275,1498,1288],{"class":1280},[1275,1500,1292],{"class":1291},[1275,1502,1295],{"class":1284},[1275,1504,1505,1507,1510,1512,1515],{"class":1277,"line":329},[1275,1506,1281],{"class":1280},[1275,1508,1509],{"class":1284}," { CounterService } ",[1275,1511,1288],{"class":1280},[1275,1513,1514],{"class":1291}," '.\u002Fcounter.service'",[1275,1516,1295],{"class":1284},[1275,1518,1519],{"class":1277,"line":318},[1275,1520,1301],{"emptyLinePlaceholder":1300},[1275,1522,1523,1525,1528],{"class":1277,"line":134},[1275,1524,1326],{"class":1284},[1275,1526,1527],{"class":1329},"Component",[1275,1529,1530],{"class":1284},"({\n",[1275,1532,1533,1536,1539],{"class":1277,"line":122},[1275,1534,1535],{"class":1284},"  selector: ",[1275,1537,1538],{"class":1291},"'app-counter'",[1275,1540,1541],{"class":1284},",\n",[1275,1543,1544,1547,1550],{"class":1277,"line":31},[1275,1545,1546],{"class":1284},"  templateUrl: ",[1275,1548,1549],{"class":1291},"'.\u002Fcounter.component.html'",[1275,1551,1541],{"class":1284},[1275,1553,1554,1557,1560],{"class":1277,"line":17},[1275,1555,1556],{"class":1284},"  styleUrl: ",[1275,1558,1559],{"class":1291},"'.\u002Fcounter.component.css'",[1275,1561,1541],{"class":1284},[1275,1563,1564],{"class":1277,"line":110},[1275,1565,1566],{"class":1284},"})\n",[1275,1568,1569,1571,1573,1576,1578,1580],{"class":1277,"line":76},[1275,1570,1338],{"class":1280},[1275,1572,1341],{"class":1280},[1275,1574,1575],{"class":1344}," CounterComponent",[1275,1577,1348],{"class":1280},[1275,1579,1352],{"class":1351},[1275,1581,1355],{"class":1284},[1275,1583,1584,1586,1588,1590,1593,1596,1599],{"class":1277,"line":247},[1275,1585,1360],{"class":1280},[1275,1587,1364],{"class":1363},[1275,1589,1367],{"class":1280},[1275,1591,1592],{"class":1329}," input",[1275,1594,1595],{"class":1284},"\u003C",[1275,1597,1598],{"class":1314},"string",[1275,1600,1601],{"class":1284},">();\n",[1275,1603,1604,1606,1609,1611,1614],{"class":1277,"line":236},[1275,1605,1360],{"class":1280},[1275,1607,1608],{"class":1363}," counterService",[1275,1610,1367],{"class":1280},[1275,1612,1613],{"class":1329}," inject",[1275,1615,1616],{"class":1284},"(CounterService);\n",[1275,1618,1619],{"class":1277,"line":225},[1275,1620,1301],{"emptyLinePlaceholder":1300},[1275,1622,1623,1625],{"class":1277,"line":214},[1275,1624,1382],{"class":1280},[1275,1626,1385],{"class":1284},[1275,1628,1629,1631,1633,1635,1638],{"class":1277,"line":203},[1275,1630,1390],{"class":1284},[1275,1632,1393],{"class":1329},[1275,1634,1396],{"class":1284},[1275,1636,1637],{"class":1291},"'CounterComponent created'",[1275,1639,1413],{"class":1284},[1275,1641,1642],{"class":1277,"line":192},[1275,1643,1418],{"class":1284},[1275,1645,1646],{"class":1277,"line":181},[1275,1647,1301],{"emptyLinePlaceholder":1300},[1275,1649,1650,1652],{"class":1277,"line":170},[1275,1651,1427],{"class":1329},[1275,1653,1385],{"class":1284},[1275,1655,1656,1658,1660,1662,1665],{"class":1277,"line":159},[1275,1657,1390],{"class":1284},[1275,1659,1393],{"class":1329},[1275,1661,1396],{"class":1284},[1275,1663,1664],{"class":1291},"'CounterComponent destroyed'",[1275,1666,1413],{"class":1284},[1275,1668,1669],{"class":1277,"line":148},[1275,1670,1418],{"class":1284},[1275,1672,1673],{"class":1277,"line":137},[1275,1674,1459],{"class":1284},[1216,1676,1677],{},[1220,1678,1679],{},"counter\u002Fcounter.component.html",[1266,1681,1685],{"className":1682,"code":1683,"language":1684,"meta":1271,"style":1271},"language-html shiki shiki-themes github-light github-dark-dimmed","\u003Ch2>Counter 頁面\u003C\u002Fh2>\n\n\u003Cp>Route ID：{{ id() }}\u003C\u002Fp>\n\u003Cp>Service ID：{{ counterService.id }}\u003C\u002Fp>\n","html",[1220,1686,1687,1702,1706,1719],{"__ignoreMap":1271},[1275,1688,1689,1691,1694,1697,1699],{"class":1277,"line":340},[1275,1690,1595],{"class":1284},[1275,1692,1245],{"class":1693},"sIAta",[1275,1695,1696],{"class":1284},">Counter 頁面\u003C\u002F",[1275,1698,1245],{"class":1693},[1275,1700,1701],{"class":1284},">\n",[1275,1703,1704],{"class":1277,"line":329},[1275,1705,1301],{"emptyLinePlaceholder":1300},[1275,1707,1708,1710,1712,1715,1717],{"class":1277,"line":318},[1275,1709,1595],{"class":1284},[1275,1711,1216],{"class":1693},[1275,1713,1714],{"class":1284},">Route ID：{{ id() }}\u003C\u002F",[1275,1716,1216],{"class":1693},[1275,1718,1701],{"class":1284},[1275,1720,1721,1723,1725,1728,1730],{"class":1277,"line":134},[1275,1722,1595],{"class":1284},[1275,1724,1216],{"class":1693},[1275,1726,1727],{"class":1284},">Service ID：{{ counterService.id }}\u003C\u002F",[1275,1729,1216],{"class":1693},[1275,1731,1701],{"class":1284},[1216,1733,1734],{},"畫面會顯示路由參數與 Service ID，方便觀察兩者是否會隨著路由切換而重新建立。",[1736,1737,1739],"h3",{"id":1738},"設定-route-providers","設定 Route Providers",[1216,1741,1742],{},"接著設定首頁與 Counter 頁面兩個路由。",[1216,1744,1745],{},[1220,1746,1747],{},"app.routes.ts",[1266,1749,1751],{"className":1268,"code":1750,"language":1270,"meta":1271,"style":1271},"import { Routes } from '@angular\u002Frouter';\nimport { CounterService } from '.\u002Fcounter\u002Fcounter.service';\n\nexport const routes: Routes = [\n  {\n    path: '',\n    loadComponent: () =>\n      import('.\u002Fhome.component').then(m => m.HomeComponent),\n  },\n  {\n    path: 'counter\u002F:id',\n    loadComponent: () =>\n      import('.\u002Fcounter\u002Fcounter.component').then(\n        m => m.CounterComponent\n      ),\n    providers: [CounterService],\n  },\n];\n",[1220,1752,1753,1767,1780,1784,1805,1810,1820,1831,1858,1863,1867,1876,1884,1900,1910,1915,1920,1924],{"__ignoreMap":1271},[1275,1754,1755,1757,1760,1762,1765],{"class":1277,"line":340},[1275,1756,1281],{"class":1280},[1275,1758,1759],{"class":1284}," { Routes } ",[1275,1761,1288],{"class":1280},[1275,1763,1764],{"class":1291}," '@angular\u002Frouter'",[1275,1766,1295],{"class":1284},[1275,1768,1769,1771,1773,1775,1778],{"class":1277,"line":329},[1275,1770,1281],{"class":1280},[1275,1772,1509],{"class":1284},[1275,1774,1288],{"class":1280},[1275,1776,1777],{"class":1291}," '.\u002Fcounter\u002Fcounter.service'",[1275,1779,1295],{"class":1284},[1275,1781,1782],{"class":1277,"line":318},[1275,1783,1301],{"emptyLinePlaceholder":1300},[1275,1785,1786,1788,1791,1794,1797,1800,1802],{"class":1277,"line":134},[1275,1787,1338],{"class":1280},[1275,1789,1790],{"class":1280}," const",[1275,1792,1793],{"class":1314}," routes",[1275,1795,1796],{"class":1280},":",[1275,1798,1799],{"class":1344}," Routes",[1275,1801,1367],{"class":1280},[1275,1803,1804],{"class":1284}," [\n",[1275,1806,1807],{"class":1277,"line":122},[1275,1808,1809],{"class":1284},"  {\n",[1275,1811,1812,1815,1818],{"class":1277,"line":31},[1275,1813,1814],{"class":1284},"    path: ",[1275,1816,1817],{"class":1291},"''",[1275,1819,1541],{"class":1284},[1275,1821,1822,1825,1828],{"class":1277,"line":17},[1275,1823,1824],{"class":1329},"    loadComponent",[1275,1826,1827],{"class":1284},": () ",[1275,1829,1830],{"class":1280},"=>\n",[1275,1832,1833,1836,1838,1841,1844,1847,1849,1852,1855],{"class":1277,"line":110},[1275,1834,1835],{"class":1280},"      import",[1275,1837,1396],{"class":1284},[1275,1839,1840],{"class":1291},"'.\u002Fhome.component'",[1275,1842,1843],{"class":1284},").",[1275,1845,1846],{"class":1329},"then",[1275,1848,1396],{"class":1284},[1275,1850,1851],{"class":1363},"m",[1275,1853,1854],{"class":1280}," =>",[1275,1856,1857],{"class":1284}," m.HomeComponent),\n",[1275,1859,1860],{"class":1277,"line":76},[1275,1861,1862],{"class":1284},"  },\n",[1275,1864,1865],{"class":1277,"line":247},[1275,1866,1809],{"class":1284},[1275,1868,1869,1871,1874],{"class":1277,"line":236},[1275,1870,1814],{"class":1284},[1275,1872,1873],{"class":1291},"'counter\u002F:id'",[1275,1875,1541],{"class":1284},[1275,1877,1878,1880,1882],{"class":1277,"line":225},[1275,1879,1824],{"class":1329},[1275,1881,1827],{"class":1284},[1275,1883,1830],{"class":1280},[1275,1885,1886,1888,1890,1893,1895,1897],{"class":1277,"line":214},[1275,1887,1835],{"class":1280},[1275,1889,1396],{"class":1284},[1275,1891,1892],{"class":1291},"'.\u002Fcounter\u002Fcounter.component'",[1275,1894,1843],{"class":1284},[1275,1896,1846],{"class":1329},[1275,1898,1899],{"class":1284},"(\n",[1275,1901,1902,1905,1907],{"class":1277,"line":203},[1275,1903,1904],{"class":1363},"        m",[1275,1906,1854],{"class":1280},[1275,1908,1909],{"class":1284}," m.CounterComponent\n",[1275,1911,1912],{"class":1277,"line":192},[1275,1913,1914],{"class":1284},"      ),\n",[1275,1916,1917],{"class":1277,"line":181},[1275,1918,1919],{"class":1284},"    providers: [CounterService],\n",[1275,1921,1922],{"class":1277,"line":170},[1275,1923,1862],{"class":1284},[1275,1925,1926],{"class":1277,"line":159},[1275,1927,1928],{"class":1284},"];\n",[1216,1930,1931,1932,1934,1935,1938,1939,1941],{},"這裡將 ",[1220,1933,1254],{}," 註冊在 ",[1220,1936,1937],{},"counter\u002F:id"," 路由的 ",[1220,1940,1222],{},"，而不是 Root 或 Component。",[1216,1943,1944],{},"Angular 的 DI 主要分成兩種 Injector 階層：",[1946,1947,1948,1977],"ul",{},[1949,1950,1951,1956,1957],"li",{},[1234,1952,1953],{},[1220,1954,1955],{},"EnvironmentInjector","：管理特定環境的依賴，包含 Root Injector 與 Route Injector。\n",[1946,1958,1959,1969],{},[1949,1960,1961,1964,1965,1968],{},[1234,1962,1963],{},"Root Injector","：管理 Application 層級的 Service，通常透過 ",[1220,1966,1967],{},"providedIn: 'root'"," 註冊。",[1949,1970,1971,1974,1975,1968],{},[1234,1972,1973],{},"Route Injector","：管理特定路由及其子路由的 Service，透過 Route ",[1220,1976,1222],{},[1949,1978,1979,1984,1985,1987],{},[1234,1980,1981],{},[1220,1982,1983],{},"ElementInjector","：管理 Component 與 Directive 的依賴，例如透過 Component 的 ",[1220,1986,1222],{}," 註冊 Service。",[1216,1989,1990,1991,1993],{},"這次使用的 Route Providers 屬於 ",[1220,1992,1955],{}," 階層。當 Router 需要這個路由提供的依賴時，就會建立對應的 Injector，管理其中的 Service。",[1216,1995,1996,1997,2000],{},"接著在 ",[1220,1998,1999],{},"app.html"," 加入導覽連結：",[1266,2002,2004],{"className":1682,"code":2003,"language":1684,"meta":1271,"style":1271},"\u003Cnav>\n  \u003Ca routerLink=\"\u002F\">首頁\u003C\u002Fa>\n  |\n  \u003Ca routerLink=\"\u002Fcounter\u002F1\">Counter 1\u003C\u002Fa>\n  |\n  \u003Ca routerLink=\"\u002Fcounter\u002F2\">Counter 2\u003C\u002Fa>\n\u003C\u002Fnav>\n\n\u003Crouter-outlet \u002F>\n",[1220,2005,2006,2015,2038,2043,2063,2067,2087,2096,2100],{"__ignoreMap":1271},[1275,2007,2008,2010,2013],{"class":1277,"line":340},[1275,2009,1595],{"class":1284},[1275,2011,2012],{"class":1693},"nav",[1275,2014,1701],{"class":1284},[1275,2016,2017,2020,2023,2026,2028,2031,2034,2036],{"class":1277,"line":329},[1275,2018,2019],{"class":1284},"  \u003C",[1275,2021,2022],{"class":1693},"a",[1275,2024,2025],{"class":1351}," routerLink",[1275,2027,1311],{"class":1284},[1275,2029,2030],{"class":1291},"\"\u002F\"",[1275,2032,2033],{"class":1284},">首頁\u003C\u002F",[1275,2035,2022],{"class":1693},[1275,2037,1701],{"class":1284},[1275,2039,2040],{"class":1277,"line":318},[1275,2041,2042],{"class":1284},"  |\n",[1275,2044,2045,2047,2049,2051,2053,2056,2059,2061],{"class":1277,"line":134},[1275,2046,2019],{"class":1284},[1275,2048,2022],{"class":1693},[1275,2050,2025],{"class":1351},[1275,2052,1311],{"class":1284},[1275,2054,2055],{"class":1291},"\"\u002Fcounter\u002F1\"",[1275,2057,2058],{"class":1284},">Counter 1\u003C\u002F",[1275,2060,2022],{"class":1693},[1275,2062,1701],{"class":1284},[1275,2064,2065],{"class":1277,"line":122},[1275,2066,2042],{"class":1284},[1275,2068,2069,2071,2073,2075,2077,2080,2083,2085],{"class":1277,"line":31},[1275,2070,2019],{"class":1284},[1275,2072,2022],{"class":1693},[1275,2074,2025],{"class":1351},[1275,2076,1311],{"class":1284},[1275,2078,2079],{"class":1291},"\"\u002Fcounter\u002F2\"",[1275,2081,2082],{"class":1284},">Counter 2\u003C\u002F",[1275,2084,2022],{"class":1693},[1275,2086,1701],{"class":1284},[1275,2088,2089,2092,2094],{"class":1277,"line":17},[1275,2090,2091],{"class":1284},"\u003C\u002F",[1275,2093,2012],{"class":1693},[1275,2095,1701],{"class":1284},[1275,2097,2098],{"class":1277,"line":110},[1275,2099,1301],{"emptyLinePlaceholder":1300},[1275,2101,2102,2104,2107],{"class":1277,"line":76},[1275,2103,1595],{"class":1284},[1275,2105,2106],{"class":1693},"router-outlet",[1275,2108,2109],{"class":1284}," \u002F>\n",[1216,2111,2112,2115,2116,2119,2120,2123],{},[1220,2113,2114],{},"app.ts"," 則引入 ",[1220,2117,2118],{},"RouterLink"," 與 ",[1220,2121,2122],{},"RouterOutlet","：",[1266,2125,2127],{"className":1268,"code":2126,"language":1270,"meta":1271,"style":1271},"import { Component } from '@angular\u002Fcore';\nimport { RouterLink, RouterOutlet } from '@angular\u002Frouter';\n\n@Component({\n  selector: 'app-root',\n  imports: [RouterLink, RouterOutlet],\n  templateUrl: '.\u002Fapp.html',\n  styleUrl: '.\u002Fapp.css',\n})\nexport class App {}\n",[1220,2128,2129,2142,2155,2159,2167,2176,2181,2190,2199,2203],{"__ignoreMap":1271},[1275,2130,2131,2133,2136,2138,2140],{"class":1277,"line":340},[1275,2132,1281],{"class":1280},[1275,2134,2135],{"class":1284}," { Component } ",[1275,2137,1288],{"class":1280},[1275,2139,1292],{"class":1291},[1275,2141,1295],{"class":1284},[1275,2143,2144,2146,2149,2151,2153],{"class":1277,"line":329},[1275,2145,1281],{"class":1280},[1275,2147,2148],{"class":1284}," { RouterLink, RouterOutlet } ",[1275,2150,1288],{"class":1280},[1275,2152,1764],{"class":1291},[1275,2154,1295],{"class":1284},[1275,2156,2157],{"class":1277,"line":318},[1275,2158,1301],{"emptyLinePlaceholder":1300},[1275,2160,2161,2163,2165],{"class":1277,"line":134},[1275,2162,1326],{"class":1284},[1275,2164,1527],{"class":1329},[1275,2166,1530],{"class":1284},[1275,2168,2169,2171,2174],{"class":1277,"line":122},[1275,2170,1535],{"class":1284},[1275,2172,2173],{"class":1291},"'app-root'",[1275,2175,1541],{"class":1284},[1275,2177,2178],{"class":1277,"line":31},[1275,2179,2180],{"class":1284},"  imports: [RouterLink, RouterOutlet],\n",[1275,2182,2183,2185,2188],{"class":1277,"line":17},[1275,2184,1546],{"class":1284},[1275,2186,2187],{"class":1291},"'.\u002Fapp.html'",[1275,2189,1541],{"class":1284},[1275,2191,2192,2194,2197],{"class":1277,"line":110},[1275,2193,1556],{"class":1284},[1275,2195,2196],{"class":1291},"'.\u002Fapp.css'",[1275,2198,1541],{"class":1284},[1275,2200,2201],{"class":1277,"line":76},[1275,2202,1566],{"class":1284},[1275,2204,2205,2207,2209,2212],{"class":1277,"line":247},[1275,2206,1338],{"class":1280},[1275,2208,1341],{"class":1280},[1275,2210,2211],{"class":1344}," App",[1275,2213,2214],{"class":1284}," {}\n",[1216,2216,2217],{},"首頁只需要簡單的內容，方便切換路由。",[1216,2219,2220],{},[1220,2221,2222],{},"home.component.ts",[1266,2224,2226],{"className":1268,"code":2225,"language":1270,"meta":1271,"style":1271},"import { Component } from '@angular\u002Fcore';\n\n@Component({\n  selector: 'app-home',\n  template: `\u003Ch2>首頁\u003C\u002Fh2>`,\n})\nexport class HomeComponent {}\n",[1220,2227,2228,2240,2244,2252,2261,2271,2275],{"__ignoreMap":1271},[1275,2229,2230,2232,2234,2236,2238],{"class":1277,"line":340},[1275,2231,1281],{"class":1280},[1275,2233,2135],{"class":1284},[1275,2235,1288],{"class":1280},[1275,2237,1292],{"class":1291},[1275,2239,1295],{"class":1284},[1275,2241,2242],{"class":1277,"line":329},[1275,2243,1301],{"emptyLinePlaceholder":1300},[1275,2245,2246,2248,2250],{"class":1277,"line":318},[1275,2247,1326],{"class":1284},[1275,2249,1527],{"class":1329},[1275,2251,1530],{"class":1284},[1275,2253,2254,2256,2259],{"class":1277,"line":134},[1275,2255,1535],{"class":1284},[1275,2257,2258],{"class":1291},"'app-home'",[1275,2260,1541],{"class":1284},[1275,2262,2263,2266,2269],{"class":1277,"line":122},[1275,2264,2265],{"class":1284},"  template: ",[1275,2267,2268],{"class":1291},"`\u003Ch2>首頁\u003C\u002Fh2>`",[1275,2270,1541],{"class":1284},[1275,2272,2273],{"class":1277,"line":31},[1275,2274,1566],{"class":1284},[1275,2276,2277,2279,2281,2284],{"class":1277,"line":17},[1275,2278,1338],{"class":1280},[1275,2280,1341],{"class":1280},[1275,2282,2283],{"class":1344}," HomeComponent",[1275,2285,2214],{"class":1284},[1216,2287,2288],{},"設定 Router，先不加入自動清理功能。",[1216,2290,2291],{},[1220,2292,2293],{},"app.config.ts",[1266,2295,2297],{"className":1268,"code":2296,"language":1270,"meta":1271,"style":1271},"import {\n  ApplicationConfig,\n  provideBrowserGlobalErrorListeners,\n} from '@angular\u002Fcore';\n\nimport {\n  provideRouter,\n  withComponentInputBinding,\n} from '@angular\u002Frouter';\n\nimport { routes } from '.\u002Fapp.routes';\n\nexport const appConfig: ApplicationConfig = {\n  providers: [\n    provideBrowserGlobalErrorListeners(),\n    provideRouter(\n      routes,\n      withComponentInputBinding()\n    ),\n  ],\n};\n",[1220,2298,2299,2305,2310,2315,2326,2330,2336,2341,2346,2356,2360,2374,2378,2396,2401,2409,2416,2421,2428,2433,2438],{"__ignoreMap":1271},[1275,2300,2301,2303],{"class":1277,"line":340},[1275,2302,1281],{"class":1280},[1275,2304,1355],{"class":1284},[1275,2306,2307],{"class":1277,"line":329},[1275,2308,2309],{"class":1284},"  ApplicationConfig,\n",[1275,2311,2312],{"class":1277,"line":318},[1275,2313,2314],{"class":1284},"  provideBrowserGlobalErrorListeners,\n",[1275,2316,2317,2320,2322,2324],{"class":1277,"line":134},[1275,2318,2319],{"class":1284},"} ",[1275,2321,1288],{"class":1280},[1275,2323,1292],{"class":1291},[1275,2325,1295],{"class":1284},[1275,2327,2328],{"class":1277,"line":122},[1275,2329,1301],{"emptyLinePlaceholder":1300},[1275,2331,2332,2334],{"class":1277,"line":31},[1275,2333,1281],{"class":1280},[1275,2335,1355],{"class":1284},[1275,2337,2338],{"class":1277,"line":17},[1275,2339,2340],{"class":1284},"  provideRouter,\n",[1275,2342,2343],{"class":1277,"line":110},[1275,2344,2345],{"class":1284},"  withComponentInputBinding,\n",[1275,2347,2348,2350,2352,2354],{"class":1277,"line":76},[1275,2349,2319],{"class":1284},[1275,2351,1288],{"class":1280},[1275,2353,1764],{"class":1291},[1275,2355,1295],{"class":1284},[1275,2357,2358],{"class":1277,"line":247},[1275,2359,1301],{"emptyLinePlaceholder":1300},[1275,2361,2362,2364,2367,2369,2372],{"class":1277,"line":236},[1275,2363,1281],{"class":1280},[1275,2365,2366],{"class":1284}," { routes } ",[1275,2368,1288],{"class":1280},[1275,2370,2371],{"class":1291}," '.\u002Fapp.routes'",[1275,2373,1295],{"class":1284},[1275,2375,2376],{"class":1277,"line":225},[1275,2377,1301],{"emptyLinePlaceholder":1300},[1275,2379,2380,2382,2384,2387,2389,2392,2394],{"class":1277,"line":214},[1275,2381,1338],{"class":1280},[1275,2383,1790],{"class":1280},[1275,2385,2386],{"class":1314}," appConfig",[1275,2388,1796],{"class":1280},[1275,2390,2391],{"class":1344}," ApplicationConfig",[1275,2393,1367],{"class":1280},[1275,2395,1355],{"class":1284},[1275,2397,2398],{"class":1277,"line":203},[1275,2399,2400],{"class":1284},"  providers: [\n",[1275,2402,2403,2406],{"class":1277,"line":192},[1275,2404,2405],{"class":1329},"    provideBrowserGlobalErrorListeners",[1275,2407,2408],{"class":1284},"(),\n",[1275,2410,2411,2414],{"class":1277,"line":181},[1275,2412,2413],{"class":1329},"    provideRouter",[1275,2415,1899],{"class":1284},[1275,2417,2418],{"class":1277,"line":170},[1275,2419,2420],{"class":1284},"      routes,\n",[1275,2422,2423,2426],{"class":1277,"line":159},[1275,2424,2425],{"class":1329},"      withComponentInputBinding",[1275,2427,1333],{"class":1284},[1275,2429,2430],{"class":1277,"line":148},[1275,2431,2432],{"class":1284},"    ),\n",[1275,2434,2435],{"class":1277,"line":137},[1275,2436,2437],{"class":1284},"  ],\n",[1275,2439,2440],{"class":1277,"line":125},[1275,2441,2442],{"class":1284},"};\n",[1216,2444,2445,2446,2449,2450,2453,2454,2456,2457,2460],{},"這裡使用 ",[1220,2447,2448],{},"withComponentInputBinding()","，讓 Router 自動將 ",[1220,2451,2452],{},":id"," 綁定到 Component 的 ",[1220,2455,1407],{}," Input，不需要另外透過 ",[1220,2458,2459],{},"ActivatedRoute"," 監聽參數。",[1736,2462,2463],{"id":2463},"觀察執行結果",[1216,2465,2466],{},"現在打開瀏覽器的 Console，從首頁切換到 Counter 1。",[1216,2468,2469],{},"第一次進入時，會看到：",[1266,2471,2476],{"className":2472,"code":2474,"language":2475,"meta":1271},[2473],"language-text","CounterService #1 created\nCounterComponent created\n","text",[1220,2477,2474],{"__ignoreMap":1271},[1216,2479,2480],{},"畫面顯示：",[1266,2482,2485],{"className":2483,"code":2484,"language":2475,"meta":1271},[2473],"Route ID：1\nService ID：1\n",[1220,2486,2484],{"__ignoreMap":1271},[1216,2488,2489],{},"接著切換到 Counter 2：",[1266,2491,2494],{"className":2492,"code":2493,"language":2475,"meta":1271},[2473],"Route ID：2\nService ID：1\n",[1220,2495,2493],{"__ignoreMap":1271},[1216,2497,2498,2499,2502,2503,2506],{},"這時不會有新的 ",[1220,2500,2501],{},"created"," 或 ",[1220,2504,2505],{},"destroyed"," 訊息，因為兩個網址使用相同的 Route Configuration，Angular 預設會重用 Component 與 Service。",[1216,2508,2509],{},"再返回首頁：",[1266,2511,2514],{"className":2512,"code":2513,"language":2475,"meta":1271},[2473],"CounterComponent destroyed\n",[1220,2515,2513],{"__ignoreMap":1271},[1216,2517,2518,2519],{},"這時會發現，",[1234,2520,2521,2522,2524,2525,1243],{},"Component 已經銷毀，但 ",[1220,2523,1254],{}," 並沒有執行 ",[1220,2526,2527],{},"ngOnDestroy()",[1216,2529,2530,2531,2534,2535,1243],{},"如果再次進入 Counter 1，畫面仍然顯示 ",[1220,2532,2533],{},"Service ID：1","，也不會再次輸出 ",[1220,2536,2537],{},"CounterService created",[1216,2539,2540,2541,2543],{},"這是因為 Route Providers 所建立的 ",[1220,2542,1955],{},"，預設不會因為離開路由就立即銷毀。當再次進入相同的 Route Configuration 時，仍然會使用原本的 Service 實例。",[1216,2545,2546,2547],{},"因此，",[1234,2548,2549],{},"Component 與 Route Provider 有各自的生命週期，即使 Component 已經銷毀，Service 仍然可能存在。",[1216,2551,2552],{},[2553,2554],"img",{"alt":2555,"src":2556},"Angular Route Provider 生命週期比較","https:\u002F\u002Fres.cloudinary.com\u002Fdseg0uwc9\u002Fimage\u002Fupload\u002Fv1791987629\u002F2026%20%E9%90%B5%E4%BA%BA%E8%B3%BD\u002FDay%2030%EF%BC%9AAngular%20Router%20Providers%20%E8%88%87%E7%94%9F%E5%91%BD%E9%80%B1%E6%9C%9F%E7%AE%A1%E7%90%86%EF%BC%8C%E8%B7%AF%E7%94%B1%E9%9B%A2%E9%96%8B%E5%BE%8C%20Service%20%E6%9C%83%E9%8A%B7%E6%AF%80%E5%97%8E%EF%BC%9F\u002FAngular%20Route%20Provider%20%E7%94%9F%E5%91%BD%E9%80%B1%E6%9C%9F%E6%AF%94%E8%BC%83.png",[1245,2558,1242],{"id":2559},"withautocleanupinjectors",[1216,2561,2562,2563,1243],{},"如果希望離開路由後，能自動清理不再使用的 Route Injector，Angular Router 提供了 ",[1220,2564,1242],{},[1216,2566,2567,2568,2571],{},"這個功能在 Angular 22.2 成為 Stable API，只需要在 ",[1220,2569,2570],{},"provideRouter()"," 加入設定即可。",[1216,2573,2574],{},[1220,2575,2293],{},[1266,2577,2579],{"className":1268,"code":2578,"language":1270,"meta":1271,"style":1271},"import {\n  ApplicationConfig,\n  provideBrowserGlobalErrorListeners,\n} from '@angular\u002Fcore';\n\nimport {\n  provideRouter,\n  withComponentInputBinding,\n  withAutoCleanupInjectors,\n} from '@angular\u002Frouter';\n\nimport { routes } from '.\u002Fapp.routes';\n\nexport const appConfig: ApplicationConfig = {\n  providers: [\n    provideBrowserGlobalErrorListeners(),\n    provideRouter(\n      routes,\n      withComponentInputBinding(),\n      withAutoCleanupInjectors(),\n    ),\n  ],\n};\n",[1220,2580,2581,2587,2591,2595,2605,2609,2615,2619,2623,2628,2638,2642,2654,2658,2674,2678,2684,2690,2694,2700,2707,2711,2715],{"__ignoreMap":1271},[1275,2582,2583,2585],{"class":1277,"line":340},[1275,2584,1281],{"class":1280},[1275,2586,1355],{"class":1284},[1275,2588,2589],{"class":1277,"line":329},[1275,2590,2309],{"class":1284},[1275,2592,2593],{"class":1277,"line":318},[1275,2594,2314],{"class":1284},[1275,2596,2597,2599,2601,2603],{"class":1277,"line":134},[1275,2598,2319],{"class":1284},[1275,2600,1288],{"class":1280},[1275,2602,1292],{"class":1291},[1275,2604,1295],{"class":1284},[1275,2606,2607],{"class":1277,"line":122},[1275,2608,1301],{"emptyLinePlaceholder":1300},[1275,2610,2611,2613],{"class":1277,"line":31},[1275,2612,1281],{"class":1280},[1275,2614,1355],{"class":1284},[1275,2616,2617],{"class":1277,"line":17},[1275,2618,2340],{"class":1284},[1275,2620,2621],{"class":1277,"line":110},[1275,2622,2345],{"class":1284},[1275,2624,2625],{"class":1277,"line":76},[1275,2626,2627],{"class":1284},"  withAutoCleanupInjectors,\n",[1275,2629,2630,2632,2634,2636],{"class":1277,"line":247},[1275,2631,2319],{"class":1284},[1275,2633,1288],{"class":1280},[1275,2635,1764],{"class":1291},[1275,2637,1295],{"class":1284},[1275,2639,2640],{"class":1277,"line":236},[1275,2641,1301],{"emptyLinePlaceholder":1300},[1275,2643,2644,2646,2648,2650,2652],{"class":1277,"line":225},[1275,2645,1281],{"class":1280},[1275,2647,2366],{"class":1284},[1275,2649,1288],{"class":1280},[1275,2651,2371],{"class":1291},[1275,2653,1295],{"class":1284},[1275,2655,2656],{"class":1277,"line":214},[1275,2657,1301],{"emptyLinePlaceholder":1300},[1275,2659,2660,2662,2664,2666,2668,2670,2672],{"class":1277,"line":203},[1275,2661,1338],{"class":1280},[1275,2663,1790],{"class":1280},[1275,2665,2386],{"class":1314},[1275,2667,1796],{"class":1280},[1275,2669,2391],{"class":1344},[1275,2671,1367],{"class":1280},[1275,2673,1355],{"class":1284},[1275,2675,2676],{"class":1277,"line":192},[1275,2677,2400],{"class":1284},[1275,2679,2680,2682],{"class":1277,"line":181},[1275,2681,2405],{"class":1329},[1275,2683,2408],{"class":1284},[1275,2685,2686,2688],{"class":1277,"line":170},[1275,2687,2413],{"class":1329},[1275,2689,1899],{"class":1284},[1275,2691,2692],{"class":1277,"line":159},[1275,2693,2420],{"class":1284},[1275,2695,2696,2698],{"class":1277,"line":148},[1275,2697,2425],{"class":1329},[1275,2699,2408],{"class":1284},[1275,2701,2702,2705],{"class":1277,"line":137},[1275,2703,2704],{"class":1329},"      withAutoCleanupInjectors",[1275,2706,2408],{"class":1284},[1275,2708,2709],{"class":1277,"line":125},[1275,2710,2432],{"class":1284},[1275,2712,2713],{"class":1277,"line":113},[1275,2714,2437],{"class":1284},[1275,2716,2717],{"class":1277,"line":101},[1275,2718,2442],{"class":1284},[1216,2720,2721],{},"原本的 Route、Component 和 Service 都不用修改。",[1736,2723,2724],{"id":2724},"再次觀察執行結果",[1216,2726,2727],{},"重新整理頁面，再從首頁進入 Counter 1。",[1266,2729,2731],{"className":2730,"code":2474,"language":2475,"meta":1271},[2473],[1220,2732,2474],{"__ignoreMap":1271},[1216,2734,2735,2736,2739,2740,2743],{},"接著切換到 Counter 2，畫面上的 Route ID 會變成 ",[1220,2737,2738],{},"2","，但 Service ID 仍然是 ",[1220,2741,2742],{},"1","，Component 和 Service 都沒有重新建立。",[1216,2745,2746],{},"這次返回首頁時，Console 會顯示：",[1266,2748,2751],{"className":2749,"code":2750,"language":2475,"meta":1271},[2473],"CounterComponent destroyed\nCounterService #1 destroyed\n",[1220,2752,2750],{"__ignoreMap":1271},[1216,2754,2755,2756,2758,2759,2761],{},"除了 Component，",[1220,2757,1254],{}," 的 ",[1220,2760,2527],{}," 也執行了。",[1216,2763,2764],{},"如果再次進入 Counter 1：",[1266,2766,2769],{"className":2767,"code":2768,"language":2475,"meta":1271},[2473],"CounterService #2 created\nCounterComponent created\n",[1220,2770,2768],{"__ignoreMap":1271},[1216,2772,2773,2774,2776],{},"畫面上的 Service ID 也會變成 ",[1220,2775,2738],{},"，表示 Router 重新建立了 Injector 與 Service 實例。",[1216,2778,2779],{},"比較兩種設定的差異：",[2781,2782,2783,2799],"table",{},[2784,2785,2786],"thead",{},[2787,2788,2789,2793,2796],"tr",{},[2790,2791,2792],"th",{},"行為",[2790,2794,2795],{},"預設設定",[2790,2797,2798],{},"啟用自動清理",[2800,2801,2802,2813,2824,2835],"tbody",{},[2787,2803,2804,2808,2811],{},[2805,2806,2807],"td",{},"離開路由時銷毀 Component",[2805,2809,2810],{},"是",[2805,2812,2810],{},[2787,2814,2815,2818,2821],{},[2805,2816,2817],{},"清理不再使用的 Route Injector",[2805,2819,2820],{},"不會自動清理",[2805,2822,2823],{},"會自動清理",[2787,2825,2826,2829,2832],{},[2805,2827,2828],{},"再次進入相同路由",[2805,2830,2831],{},"重用原本的 Service",[2805,2833,2834],{},"建立新的 Service",[2787,2836,2837,2842,2845],{},[2805,2838,2839,2840],{},"Service ",[1220,2841,2527],{},[2805,2843,2844],{},"不會因離開路由而觸發",[2805,2846,2847],{},"Injector 銷毀時觸發",[1216,2849,2850,2851,2853,2854,2857],{},"不過，",[1220,2852,1242],{}," 並不是每次切換路由都會銷毀所有 Service。Router 會在導航完成後，檢查哪些 Route Injector 已經不再使用，再配合 ",[1220,2855,2856],{},"RouteReuseStrategy"," 決定是否清理。",[1216,2859,2860],{},[2553,2861],{"alt":2862,"src":2863},"Angular Router Providers 生命週期：預設設定與自動清理的差異","https:\u002F\u002Fres.cloudinary.com\u002Fdseg0uwc9\u002Fimage\u002Fupload\u002Fv1791960049\u002F2026%20%E9%90%B5%E4%BA%BA%E8%B3%BD\u002FDay%2030%EF%BC%9AAngular%20Router%20Providers%20%E8%88%87%E7%94%9F%E5%91%BD%E9%80%B1%E6%9C%9F%E7%AE%A1%E7%90%86%EF%BC%8C%E8%B7%AF%E7%94%B1%E9%9B%A2%E9%96%8B%E5%BE%8C%20Service%20%E6%9C%83%E9%8A%B7%E6%AF%80%E5%97%8E%EF%BC%9F\u002Frouter-providers-lifecycle-v2.png",[1245,2865,2867],{"id":2866},"routereusestrategy-與-injector-清理","RouteReuseStrategy 與 Injector 清理",[1216,2869,2870,2871,2873,2874,2876],{},"在 Day 23 已經介紹過 ",[1220,2872,2856],{}," 的基本用法，這裡補充它與 ",[1220,2875,1242],{}," 的關係。",[1216,2878,2879,2880,2882],{},"當 Router 啟用自動清理後，除了目前正在使用的路由，也要考慮被 ",[1220,2881,2856],{}," 保存的路由。如果 Component 只是暫時被 detach，對應的 Injector 也需要保留，否則之後重新 attach 時可能發生問題。",[1216,2884,2885,2886,2888],{},"為了配合這個機制，",[1220,2887,2856],{}," 另外提供兩個方法：",[1946,2890,2891,2899],{},[1949,2892,2893,2898],{},[1234,2894,2895],{},[1220,2896,2897],{},"shouldDestroyInjector()","：決定 Route Injector 是否允許被銷毀。",[1949,2900,2901,2906,2907,2910],{},[1234,2902,2903],{},[1220,2904,2905],{},"retrieveStoredRouteHandles()","：回傳目前保存的 ",[1220,2908,2909],{},"DetachedRouteHandle","，讓 Router 知道哪些路由仍然需要保留。",[1216,2912,2913,2914,2916,2917,2920,2921,2923,2924,2926,2927,2929],{},"如果使用預設的 ",[1220,2915,2856],{},"，或繼承 ",[1220,2918,2919],{},"BaseRouteReuseStrategy","，",[1220,2922,2897],{}," 已經有預設行為。如果自訂策略會保存 ",[1220,2925,2909],{},"，則需要透過 ",[1220,2928,2905],{}," 提供目前保存的內容，避免對應的 Injector 被提前清理。",[1216,2931,2932,2933,2935,2936,2939,2940,2943],{},"前面的 Counter 範例也能看到，即使啟用了 ",[1220,2934,1242],{},"，從 ",[1220,2937,2938],{},"\u002Fcounter\u002F1"," 切換到 ",[1220,2941,2942],{},"\u002Fcounter\u002F2"," 時，Component 與 Service 仍然會被重用。",[1216,2945,2946],{},"這是因為兩個網址使用相同的 Route Configuration，Angular 會直接沿用目前的 Component，不需要透過 detach \u002F attach 保存與還原頁面。由於 Route Injector 仍然在使用中，因此也不會被自動清理。",[2948,2949,2950],"blockquote",{},[1216,2951,2952],{},[2022,2953,2957],{"href":2954,"rel":2955},"https:\u002F\u002Fstackblitz.com\u002Fedit\u002Fldbybozv-nep2cuuk?file=src%2Fapp%2Fcustom-route-reuse.strategy.ts",[2956],"nofollow","Angular Router Inject Service - StackBlitz",[1245,2959,2961],{"id":2960},"route-provider-與-root-provider-的清理範圍","Route Provider 與 Root Provider 的清理範圍",[1216,2963,2964,2966],{},[1220,2965,1242],{}," 只會清理不再使用的 Route Injector，不會影響 Root Injector。",[1216,2968,2969,2970,2972,2973,2975],{},"例如，前面的 ",[1220,2971,1254],{}," 沒有設定 ",[1220,2974,1967],{},"，而是透過 Route Providers 註冊：",[1266,2977,2979],{"className":1268,"code":2978,"language":1270,"meta":1271,"style":1271},"{\n  path: 'counter\u002F:id',\n  providers: [CounterService],\n}\n",[1220,2980,2981,2986,2998,3006],{"__ignoreMap":1271},[1275,2982,2983],{"class":1277,"line":340},[1275,2984,2985],{"class":1284},"{\n",[1275,2987,2988,2991,2994,2996],{"class":1277,"line":329},[1275,2989,2990],{"class":1344},"  path",[1275,2992,2993],{"class":1284},": ",[1275,2995,1873],{"class":1291},[1275,2997,1541],{"class":1284},[1275,2999,3000,3003],{"class":1277,"line":318},[1275,3001,3002],{"class":1344},"  providers",[1275,3004,3005],{"class":1284},": [CounterService],\n",[1275,3007,3008],{"class":1277,"line":134},[1275,3009,1459],{"class":1284},[1216,3011,3012,3013,3015],{},"當 Route Injector 被銷毀時，",[1220,3014,1254],{}," 也會跟著銷毀。",[1216,3017,3018],{},"但如果改成在 Root 註冊：",[1266,3020,3022],{"className":1268,"code":3021,"language":1270,"meta":1271,"style":1271},"@Injectable({\n  providedIn: 'root',\n})\nexport class CounterService {}\n",[1220,3023,3024,3032,3042,3046],{"__ignoreMap":1271},[1275,3025,3026,3028,3030],{"class":1277,"line":340},[1275,3027,1326],{"class":1284},[1275,3029,1330],{"class":1329},[1275,3031,1530],{"class":1284},[1275,3033,3034,3037,3040],{"class":1277,"line":329},[1275,3035,3036],{"class":1284},"  providedIn: ",[1275,3038,3039],{"class":1291},"'root'",[1275,3041,1541],{"class":1284},[1275,3043,3044],{"class":1277,"line":318},[1275,3045,1566],{"class":1284},[1275,3047,3048,3050,3052,3054],{"class":1277,"line":134},[1275,3049,1338],{"class":1280},[1275,3051,1341],{"class":1280},[1275,3053,1345],{"class":1344},[1275,3055,2214],{"class":1284},[1216,3057,3058],{},"而且沒有在 Route Providers 另外註冊，就會使用 Root Injector 提供的實例。即使離開 Counter 頁面，Service 也不會因此被銷毀。",[1216,3060,3061],{},"如果兩邊都有註冊，Angular 會優先使用 Route Providers 提供的實例，而 Root 的實例仍由 Root Injector 管理，兩者有各自的生命週期。",[3063,3064],"hr",{},[1245,3066,3068],{"id":3067},"這-30-天屬於自己的回憶寶藏","這 30 天屬於自己的回憶寶藏",[1216,3070,3071],{},"不知不覺，今年的鐵人賽也來到最後一天了！到了真正完賽的這一刻，心裡還是覺得很感動。",[1216,3073,3074],{},"今年其實猶豫了很久才決定參賽。一方面擔心自己沒辦法好好表達想分享的內容，另一方面也是因為過去沒有真正挑戰過連續 30 天日更。就這樣一路猶豫到報名截止前的 23:50，才終於下定決心，開始思考這次要寫什麼主題。",[1216,3076,3077],{},"之所以還是決定參加，是因為我希望自己每一年都能有所進步，哪怕只是一點點也好。同時也想藉由這次機會，重新研究那些過去沒能完全理解的觀念，看看經過 30 天的累積，自己能走到哪裡。",[1216,3079,3080,3081,3086,3087,3092],{},"說到 Angular Signal，其實前年就曾經讀過 Connie 分享的 ",[2022,3082,3085],{"href":3083,"rel":3084},"https:\u002F\u002Fithelp.ithome.com.tw\u002Fusers\u002F20168314\u002Fironman\u002F7125",[2956],"Signal 系列文章","。當時從文章中發現許多自己過去沒有深入思考的問題，也試著一篇篇跟著閱讀、動手實作，並將練習整理在 ",[2022,3088,3091],{"href":3089,"rel":3090},"https:\u002F\u002Fstackblitz.com\u002F@LING-JUN-HAO\u002Fcollections\u002Fangular-19-signal-api-it",[2956],"StackBlitz"," 上。",[1216,3094,3095],{},"從 Angular 推出 Signal 開始，我就一直很想更深入了解它，只是當時還有許多不太理解的地方。Connie 的文章讓我學到了不少，也讓我更有動力繼續探索這個主題。如果大家對 Angular Signal 有興趣，也很推薦去看看她的系列文章！",[1216,3097,3098],{},"今年除了鐵人賽，也嘗試了許多過去很想做的事情。從擔任講師、站上舞台分享，到和一群熱愛程式技術與研討會的夥伴一起籌辦 Vconf，每一件事情都讓我很期待，也希望自己能做到最好。",[1216,3100,3101,3102,1243],{},"但也因為太想把每件事情做好，有時候反而給了自己很大的壓力。甚至曾經因為覺得文章寫得不夠好，一邊修改、一邊難過到默默掉眼淚。這一年，我一直試著在這些事情之間找到自己的節奏，也慢慢體會到什麼是 ",[1234,3103,3104],{},"「有限度的完美」",[1216,3106,3107],{},"我還是希望自己能把事情做好，也不想因為時間有限就隨便應付。但有時候，真的需要接受自己的能力和時間都有極限。對我來說，有限度的完美不是降低標準，而是在自己能做到的範圍內盡力，也學著接受那些暫時還不夠好的地方。",[1216,3109,3110],{},"我想，這也是今年很重要的一個收穫吧。即使還有很多不滿意的地方，回頭看看，還是能發現自己比過去又多走了一小段路。",[1216,3112,3113,3114,3119],{},"另外，也想趁最後一天小小宣傳一下！今年很開心能以開發人員的身分參與 Vconf Taiwan 2026，和夥伴們一起完成這次的 ",[2022,3115,3118],{"href":3116,"rel":3117},"https:\u002F\u002Fv-conf.vue.tw\u002F",[2956],"官方網站","。研討會就在 10 月 17 日，如果大家對 Vue 或前端技術有興趣，也很歡迎來現場一起交流！",[1216,3121,3122],{},"最後的最後，真的很感謝這 30 天願意閱讀文章、給予鼓勵，以及陪伴我走到這裡的每一個人。",[1216,3124,3125],{},"當然，也想謝謝自己，總是允許自己那麼任性。明明知道會很辛苦，卻還是願意為了那些想做的事情，再努力試試看。",[1216,3127,3128],{},"希望未來回頭看這 30 天時，記得的不只是每天趕著完成文章的日子，還有那個即使不太有把握，仍然願意鼓起勇氣挑戰的自己。",[3130,3131,3132],"style",{},"html pre.shiki code .s7YZ4, html code.shiki .s7YZ4{--shiki-default:#D73A49;--shiki-dark:#F47067}html pre.shiki code .sYgZi, html code.shiki .sYgZi{--shiki-default:#24292E;--shiki-dark:#ADBAC7}html pre.shiki code .s-HuK, html code.shiki .s-HuK{--shiki-default:#032F62;--shiki-dark:#96D0FF}html pre.shiki code .sviXB, html code.shiki .sviXB{--shiki-default:#005CC5;--shiki-dark:#6CB6FF}html pre.shiki code .sPO5f, html code.shiki .sPO5f{--shiki-default:#6F42C1;--shiki-dark:#DCBDFB}html pre.shiki code .sOLd2, html code.shiki .sOLd2{--shiki-default:#6F42C1;--shiki-dark:#F69D50}html pre.shiki code .sMOND, html code.shiki .sMOND{--shiki-default:#6F42C1;--shiki-dark:#6CB6FF}html pre.shiki code .stnAF, html code.shiki .stnAF{--shiki-default:#E36209;--shiki-dark:#F69D50}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 .sIAta, html code.shiki .sIAta{--shiki-default:#22863A;--shiki-dark:#8DDB8C}",{"title":1271,"searchDepth":134,"depth":134,"links":3134},[3135,3139,3142,3143,3144],{"id":1247,"depth":329,"text":1248,"children":3136},[3137,3138],{"id":1738,"depth":318,"text":1739},{"id":2463,"depth":318,"text":2463},{"id":2559,"depth":329,"text":1242,"children":3140},[3141],{"id":2724,"depth":318,"text":2724},{"id":2866,"depth":329,"text":2867},{"id":2960,"depth":329,"text":2961},{"id":3067,"depth":329,"text":3068},[11,13],"md",{},"---\ntitle: \"Day 30：Angular Router Providers 與生命週期管理，路由離開後 Service 會銷毀嗎？\"\ndate: 2026-10-14 14:46:39\ntags:\n  - \"iThome 鐵人賽\"\n  - \"2026 鐵人賽\"\n  - \"Angular\"\ncategories:\n  - \"iThome 鐵人賽\"\n  - \"Angular\"\ndescription: \"平常在 Angular 中，我們可以透過 providers 決定 Service 的注入範圍。例如註冊在 Root，讓整個 Application 共用同一個實例；或註冊在 Component，讓 Service 隨著…\"\ncanonical: https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10424222\nseries:\n  name: \"2026 iThome 鐵人賽：Angular 22 Signal 進化論\"\n  url: https:\u002F\u002Fithelp.ithome.com.tw\u002Fusers\u002F20116554\u002Fironman\u002F9939\n  day: 30\n---\n\n平常在 Angular 中，我們可以透過 `providers` 決定 Service 的注入範圍。例如註冊在 Root，讓整個 Application 共用同一個實例；或註冊在 Component，讓 Service 隨著 Component 一起建立與銷毀。\n\n除了這兩種方式，Angular Router 也允許我們在 Route 中宣告 `providers`，讓特定路由及其子路由使用專屬的 Service。\n\n不過，這裡有個容易忽略的問題：**當使用者離開路由時，註冊在 Route Providers 的 Service，也會跟著銷毀嗎？**\n\n今天就透過一個簡單的範例觀察這個行為，再介紹 Angular 22.2 正式提供的 `withAutoCleanupInjectors()`。\n\n## Route Providers 的生命週期\n\n首先建立一個 `CounterService`，透過 `OnDestroy` 觀察 Service 什麼時候被銷毀。\n\n`counter\u002Fcounter.service.ts`\n\n```ts\nimport { Injectable, OnDestroy } from '@angular\u002Fcore';\n\nlet nextId = 0;\n\n@Injectable()\nexport class CounterService implements OnDestroy {\n  readonly id = ++nextId;\n\n  constructor() {\n    console.log(`CounterService #${this.id} created`);\n  }\n\n  ngOnDestroy() {\n    console.log(`CounterService #${this.id} destroyed`);\n  }\n}\n```\n\n這裡用 `nextId` 記錄 Service 建立的次數，每次建立新實例時，`id` 就會增加 1。即使 Service 被銷毀，`nextId` 也不會重設，方便區分不同的實例。\n\n接著建立 Counter 頁面，注入剛才的 Service，並使用 `input()` 接收路由參數。\n\n`counter\u002Fcounter.component.ts`\n\n```ts\nimport { Component, inject, input, OnDestroy } from '@angular\u002Fcore';\nimport { CounterService } from '.\u002Fcounter.service';\n\n@Component({\n  selector: 'app-counter',\n  templateUrl: '.\u002Fcounter.component.html',\n  styleUrl: '.\u002Fcounter.component.css',\n})\nexport class CounterComponent implements OnDestroy {\n  readonly id = input\u003Cstring>();\n  readonly counterService = inject(CounterService);\n\n  constructor() {\n    console.log('CounterComponent created');\n  }\n\n  ngOnDestroy() {\n    console.log('CounterComponent destroyed');\n  }\n}\n```\n\n`counter\u002Fcounter.component.html`\n\n```html\n\u003Ch2>Counter 頁面\u003C\u002Fh2>\n\n\u003Cp>Route ID：{{ id() }}\u003C\u002Fp>\n\u003Cp>Service ID：{{ counterService.id }}\u003C\u002Fp>\n```\n\n畫面會顯示路由參數與 Service ID，方便觀察兩者是否會隨著路由切換而重新建立。\n\n### 設定 Route Providers\n\n接著設定首頁與 Counter 頁面兩個路由。\n\n`app.routes.ts`\n\n```ts\nimport { Routes } from '@angular\u002Frouter';\nimport { CounterService } from '.\u002Fcounter\u002Fcounter.service';\n\nexport const routes: Routes = [\n  {\n    path: '',\n    loadComponent: () =>\n      import('.\u002Fhome.component').then(m => m.HomeComponent),\n  },\n  {\n    path: 'counter\u002F:id',\n    loadComponent: () =>\n      import('.\u002Fcounter\u002Fcounter.component').then(\n        m => m.CounterComponent\n      ),\n    providers: [CounterService],\n  },\n];\n```\n\n這裡將 `CounterService` 註冊在 `counter\u002F:id` 路由的 `providers`，而不是 Root 或 Component。\n\nAngular 的 DI 主要分成兩種 Injector 階層：\n\n- **`EnvironmentInjector`**：管理特定環境的依賴，包含 Root Injector 與 Route Injector。\n    - **Root Injector**：管理 Application 層級的 Service，通常透過 `providedIn: 'root'` 註冊。\n    - **Route Injector**：管理特定路由及其子路由的 Service，透過 Route `providers` 註冊。\n- **`ElementInjector`**：管理 Component 與 Directive 的依賴，例如透過 Component 的 `providers` 註冊 Service。\n\n這次使用的 Route Providers 屬於 `EnvironmentInjector` 階層。當 Router 需要這個路由提供的依賴時，就會建立對應的 Injector，管理其中的 Service。\n\n接著在 `app.html` 加入導覽連結：\n\n```html\n\u003Cnav>\n  \u003Ca routerLink=\"\u002F\">首頁\u003C\u002Fa>\n  |\n  \u003Ca routerLink=\"\u002Fcounter\u002F1\">Counter 1\u003C\u002Fa>\n  |\n  \u003Ca routerLink=\"\u002Fcounter\u002F2\">Counter 2\u003C\u002Fa>\n\u003C\u002Fnav>\n\n\u003Crouter-outlet \u002F>\n```\n\n`app.ts` 則引入 `RouterLink` 與 `RouterOutlet`：\n\n```ts\nimport { Component } from '@angular\u002Fcore';\nimport { RouterLink, RouterOutlet } from '@angular\u002Frouter';\n\n@Component({\n  selector: 'app-root',\n  imports: [RouterLink, RouterOutlet],\n  templateUrl: '.\u002Fapp.html',\n  styleUrl: '.\u002Fapp.css',\n})\nexport class App {}\n```\n\n首頁只需要簡單的內容，方便切換路由。\n\n`home.component.ts`\n\n```ts\nimport { Component } from '@angular\u002Fcore';\n\n@Component({\n  selector: 'app-home',\n  template: `\u003Ch2>首頁\u003C\u002Fh2>`,\n})\nexport class HomeComponent {}\n```\n\n設定 Router，先不加入自動清理功能。\n\n`app.config.ts`\n\n```ts\nimport {\n  ApplicationConfig,\n  provideBrowserGlobalErrorListeners,\n} from '@angular\u002Fcore';\n\nimport {\n  provideRouter,\n  withComponentInputBinding,\n} from '@angular\u002Frouter';\n\nimport { routes } from '.\u002Fapp.routes';\n\nexport const appConfig: ApplicationConfig = {\n  providers: [\n    provideBrowserGlobalErrorListeners(),\n    provideRouter(\n      routes,\n      withComponentInputBinding()\n    ),\n  ],\n};\n```\n\n這裡使用 `withComponentInputBinding()`，讓 Router 自動將 `:id` 綁定到 Component 的 `id` Input，不需要另外透過 `ActivatedRoute` 監聽參數。\n\n### 觀察執行結果\n\n現在打開瀏覽器的 Console，從首頁切換到 Counter 1。\n\n第一次進入時，會看到：\n\n```text\nCounterService #1 created\nCounterComponent created\n```\n\n畫面顯示：\n\n```text\nRoute ID：1\nService ID：1\n```\n\n接著切換到 Counter 2：\n\n```text\nRoute ID：2\nService ID：1\n```\n\n這時不會有新的 `created` 或 `destroyed` 訊息，因為兩個網址使用相同的 Route Configuration，Angular 預設會重用 Component 與 Service。\n\n再返回首頁：\n\n```text\nCounterComponent destroyed\n```\n\n這時會發現，**Component 已經銷毀，但 `CounterService` 並沒有執行 `ngOnDestroy()`。**\n\n如果再次進入 Counter 1，畫面仍然顯示 `Service ID：1`，也不會再次輸出 `CounterService created`。\n\n這是因為 Route Providers 所建立的 `EnvironmentInjector`，預設不會因為離開路由就立即銷毀。當再次進入相同的 Route Configuration 時，仍然會使用原本的 Service 實例。\n\n因此，**Component 與 Route Provider 有各自的生命週期，即使 Component 已經銷毀，Service 仍然可能存在。**\n\n![Angular Route Provider 生命週期比較](https:\u002F\u002Fres.cloudinary.com\u002Fdseg0uwc9\u002Fimage\u002Fupload\u002Fv1791987629\u002F2026%20%E9%90%B5%E4%BA%BA%E8%B3%BD\u002FDay%2030%EF%BC%9AAngular%20Router%20Providers%20%E8%88%87%E7%94%9F%E5%91%BD%E9%80%B1%E6%9C%9F%E7%AE%A1%E7%90%86%EF%BC%8C%E8%B7%AF%E7%94%B1%E9%9B%A2%E9%96%8B%E5%BE%8C%20Service%20%E6%9C%83%E9%8A%B7%E6%AF%80%E5%97%8E%EF%BC%9F\u002FAngular%20Route%20Provider%20%E7%94%9F%E5%91%BD%E9%80%B1%E6%9C%9F%E6%AF%94%E8%BC%83.png)\n\n## withAutoCleanupInjectors()\n\n如果希望離開路由後，能自動清理不再使用的 Route Injector，Angular Router 提供了 `withAutoCleanupInjectors()`。\n\n這個功能在 Angular 22.2 成為 Stable API，只需要在 `provideRouter()` 加入設定即可。\n\n`app.config.ts`\n\n```ts\nimport {\n  ApplicationConfig,\n  provideBrowserGlobalErrorListeners,\n} from '@angular\u002Fcore';\n\nimport {\n  provideRouter,\n  withComponentInputBinding,\n  withAutoCleanupInjectors,\n} from '@angular\u002Frouter';\n\nimport { routes } from '.\u002Fapp.routes';\n\nexport const appConfig: ApplicationConfig = {\n  providers: [\n    provideBrowserGlobalErrorListeners(),\n    provideRouter(\n      routes,\n      withComponentInputBinding(),\n      withAutoCleanupInjectors(),\n    ),\n  ],\n};\n```\n\n原本的 Route、Component 和 Service 都不用修改。\n\n### 再次觀察執行結果\n\n重新整理頁面，再從首頁進入 Counter 1。\n\n```text\nCounterService #1 created\nCounterComponent created\n```\n\n接著切換到 Counter 2，畫面上的 Route ID 會變成 `2`，但 Service ID 仍然是 `1`，Component 和 Service 都沒有重新建立。\n\n這次返回首頁時，Console 會顯示：\n\n```text\nCounterComponent destroyed\nCounterService #1 destroyed\n```\n\n除了 Component，`CounterService` 的 `ngOnDestroy()` 也執行了。\n\n如果再次進入 Counter 1：\n\n```text\nCounterService #2 created\nCounterComponent created\n```\n\n畫面上的 Service ID 也會變成 `2`，表示 Router 重新建立了 Injector 與 Service 實例。\n\n比較兩種設定的差異：\n\n| 行為 | 預設設定 | 啟用自動清理 |\n| --- | --- | --- |\n| 離開路由時銷毀 Component | 是 | 是 |\n| 清理不再使用的 Route Injector | 不會自動清理 | 會自動清理 |\n| 再次進入相同路由 | 重用原本的 Service | 建立新的 Service |\n| Service `ngOnDestroy()` | 不會因離開路由而觸發 | Injector 銷毀時觸發 |\n\n不過，`withAutoCleanupInjectors()` 並不是每次切換路由都會銷毀所有 Service。Router 會在導航完成後，檢查哪些 Route Injector 已經不再使用，再配合 `RouteReuseStrategy` 決定是否清理。\n\n![Angular Router Providers 生命週期：預設設定與自動清理的差異](https:\u002F\u002Fres.cloudinary.com\u002Fdseg0uwc9\u002Fimage\u002Fupload\u002Fv1791960049\u002F2026%20%E9%90%B5%E4%BA%BA%E8%B3%BD\u002FDay%2030%EF%BC%9AAngular%20Router%20Providers%20%E8%88%87%E7%94%9F%E5%91%BD%E9%80%B1%E6%9C%9F%E7%AE%A1%E7%90%86%EF%BC%8C%E8%B7%AF%E7%94%B1%E9%9B%A2%E9%96%8B%E5%BE%8C%20Service%20%E6%9C%83%E9%8A%B7%E6%AF%80%E5%97%8E%EF%BC%9F\u002Frouter-providers-lifecycle-v2.png)\n\n## RouteReuseStrategy 與 Injector 清理\n\n在 Day 23 已經介紹過 `RouteReuseStrategy` 的基本用法，這裡補充它與 `withAutoCleanupInjectors()` 的關係。\n\n當 Router 啟用自動清理後，除了目前正在使用的路由，也要考慮被 `RouteReuseStrategy` 保存的路由。如果 Component 只是暫時被 detach，對應的 Injector 也需要保留，否則之後重新 attach 時可能發生問題。\n\n為了配合這個機制，`RouteReuseStrategy` 另外提供兩個方法：\n\n- **`shouldDestroyInjector()`**：決定 Route Injector 是否允許被銷毀。\n- **`retrieveStoredRouteHandles()`**：回傳目前保存的 `DetachedRouteHandle`，讓 Router 知道哪些路由仍然需要保留。\n\n如果使用預設的 `RouteReuseStrategy`，或繼承 `BaseRouteReuseStrategy`，`shouldDestroyInjector()` 已經有預設行為。如果自訂策略會保存 `DetachedRouteHandle`，則需要透過 `retrieveStoredRouteHandles()` 提供目前保存的內容，避免對應的 Injector 被提前清理。\n\n前面的 Counter 範例也能看到，即使啟用了 `withAutoCleanupInjectors()`，從 `\u002Fcounter\u002F1` 切換到 `\u002Fcounter\u002F2` 時，Component 與 Service 仍然會被重用。\n\n這是因為兩個網址使用相同的 Route Configuration，Angular 會直接沿用目前的 Component，不需要透過 detach \u002F attach 保存與還原頁面。由於 Route Injector 仍然在使用中，因此也不會被自動清理。\n\n> [Angular Router Inject Service - StackBlitz](https:\u002F\u002Fstackblitz.com\u002Fedit\u002Fldbybozv-nep2cuuk?file=src%2Fapp%2Fcustom-route-reuse.strategy.ts)\n\n## Route Provider 與 Root Provider 的清理範圍\n\n`withAutoCleanupInjectors()` 只會清理不再使用的 Route Injector，不會影響 Root Injector。\n\n例如，前面的 `CounterService` 沒有設定 `providedIn: 'root'`，而是透過 Route Providers 註冊：\n\n```ts\n{\n  path: 'counter\u002F:id',\n  providers: [CounterService],\n}\n```\n\n當 Route Injector 被銷毀時，`CounterService` 也會跟著銷毀。\n\n但如果改成在 Root 註冊：\n\n```ts\n@Injectable({\n  providedIn: 'root',\n})\nexport class CounterService {}\n```\n\n而且沒有在 Route Providers 另外註冊，就會使用 Root Injector 提供的實例。即使離開 Counter 頁面，Service 也不會因此被銷毀。\n\n如果兩邊都有註冊，Angular 會優先使用 Route Providers 提供的實例，而 Root 的實例仍由 Root Injector 管理，兩者有各自的生命週期。\n\n* * *\n\n## 這 30 天屬於自己的回憶寶藏\n\n不知不覺，今年的鐵人賽也來到最後一天了！到了真正完賽的這一刻，心裡還是覺得很感動。\n\n今年其實猶豫了很久才決定參賽。一方面擔心自己沒辦法好好表達想分享的內容，另一方面也是因為過去沒有真正挑戰過連續 30 天日更。就這樣一路猶豫到報名截止前的 23:50，才終於下定決心，開始思考這次要寫什麼主題。\n\n之所以還是決定參加，是因為我希望自己每一年都能有所進步，哪怕只是一點點也好。同時也想藉由這次機會，重新研究那些過去沒能完全理解的觀念，看看經過 30 天的累積，自己能走到哪裡。\n\n說到 Angular Signal，其實前年就曾經讀過 Connie 分享的 [Signal 系列文章](https:\u002F\u002Fithelp.ithome.com.tw\u002Fusers\u002F20168314\u002Fironman\u002F7125)。當時從文章中發現許多自己過去沒有深入思考的問題，也試著一篇篇跟著閱讀、動手實作，並將練習整理在 [StackBlitz](https:\u002F\u002Fstackblitz.com\u002F@LING-JUN-HAO\u002Fcollections\u002Fangular-19-signal-api-it) 上。\n\n從 Angular 推出 Signal 開始，我就一直很想更深入了解它，只是當時還有許多不太理解的地方。Connie 的文章讓我學到了不少，也讓我更有動力繼續探索這個主題。如果大家對 Angular Signal 有興趣，也很推薦去看看她的系列文章！\n\n今年除了鐵人賽，也嘗試了許多過去很想做的事情。從擔任講師、站上舞台分享，到和一群熱愛程式技術與研討會的夥伴一起籌辦 Vconf，每一件事情都讓我很期待，也希望自己能做到最好。\n\n但也因為太想把每件事情做好，有時候反而給了自己很大的壓力。甚至曾經因為覺得文章寫得不夠好，一邊修改、一邊難過到默默掉眼淚。這一年，我一直試著在這些事情之間找到自己的節奏，也慢慢體會到什麼是 **「有限度的完美」**。\n\n我還是希望自己能把事情做好，也不想因為時間有限就隨便應付。但有時候，真的需要接受自己的能力和時間都有極限。對我來說，有限度的完美不是降低標準，而是在自己能做到的範圍內盡力，也學著接受那些暫時還不夠好的地方。\n\n我想，這也是今年很重要的一個收穫吧。即使還有很多不滿意的地方，回頭看看，還是能發現自己比過去又多走了一小段路。\n\n另外，也想趁最後一天小小宣傳一下！今年很開心能以開發人員的身分參與 Vconf Taiwan 2026，和夥伴們一起完成這次的 [官方網站](https:\u002F\u002Fv-conf.vue.tw\u002F)。研討會就在 10 月 17 日，如果大家對 Vue 或前端技術有興趣，也很歡迎來現場一起交流！\n\n最後的最後，真的很感謝這 30 天願意閱讀文章、給予鼓勵，以及陪伴我走到這裡的每一個人。\n\n當然，也想謝謝自己，總是允許自己那麼任性。明明知道會很辛苦，卻還是願意為了那些想做的事情，再努力試試看。\n\n希望未來回頭看這 30 天時，記得的不只是每天趕著完成文章的日子，還有那個即使不太有把握，仍然願意鼓起勇氣挑戰的自己。\n",{"title":6,"description":7},{"name":20,"url":21,"day":22},{"loc":5,"images":3152,"lastmod":8},[3153,3154],{"loc":2556},{"loc":2863},"ithome-2026-day-30","2026-10-14-ithome-2026-day-30",[11,12,13],"x14irqI1U_unmerzB3vLfoERZXT6XSsbJuEerFwy_Lo",1792575141518]