[{"data":1,"prerenderedAt":3137},["ShallowReactive",2],{"all-posts":3,"post:\u002Fithome-2026-day-15":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":184,"body":1212,"canonical":190,"categories":3121,"date":186,"description":185,"draft":15,"extension":3122,"meta":3123,"navigation":1720,"ogImage":9,"path":183,"rawbody":3124,"readingTime":17,"robots":9,"schemaOrg":9,"seo":3125,"series":3126,"sitemap":3127,"slug":3133,"stem":3134,"tags":3135,"updated":9,"wordCount":189,"__hash__":3136},"posts\u002F2026-09-29-ithome-2026-day-15.md",{"type":1213,"value":1214,"toc":3108},"minimark",[1215,1218,1230,1236,1241,1244,1261,1313,1322,1328,1366,1375,1378,1381,1385,1391,1394,1401,1406,1425,1436,1442,1449,1453,1456,1462,1465,1532,1542,1545,1613,1616,1661,1666,1739,1745,1749,1752,1758,1800,1806,1848,1854,1857,1892,1895,1900,1904,1912,1915,2051,2057,2069,2074,2077,2150,2160,2229,2241,2247,2251,2267,2270,2277,2312,2317,2378,2381,2433,2439,2446,2484,2490,2493,2516,2521,2524,2545,2554,2560,2567,2631,2640,2644,2649,2656,2659,2777,2786,2795,2801,2936,2944,2950,2962,2966,2969,2986,2992,2995,3000,3009,3020,3030,3034,3104],[1216,1217,185],"p",{},[1216,1219,1220,1221,1225,1226,1229],{},"平常使用 Angular 提供的 API 時，我們不一定會注意它們需要在哪個 Context 中執行。直到遇到 ",[1222,1223,1224],"code",{},"inject()","、",[1222,1227,1228],{},"runInInjectionContext()"," 這類 API，才會發現執行環境會直接影響函式能不能正常使用。",[1216,1231,1232,1233,1235],{},"之前同事也曾經問過我，",[1222,1234,1228],{}," 到底是拿來做什麼的。這篇就從這個問題開始，整理 Injection Context 的用途，以及它和 Reactive Context 的差別。",[1237,1238,1240],"h2",{"id":1239},"angular-di-系統","Angular DI 系統",[1216,1242,1243],{},"Angular 本身建立在一套 DI（Dependency Injection，依賴注入）系統上。",[1216,1245,1246,1247,1250,1251,1254,1255,1257,1258,1260],{},"假設 ",[1222,1248,1249],{},"A"," class 需要使用 ",[1222,1252,1253],{},"B"," class，最直接的做法是在 ",[1222,1256,1249],{}," 裡自行建立 ",[1222,1259,1253],{}," 的實例。",[1262,1263,1268],"pre",{"className":1264,"code":1265,"language":1266,"meta":1267,"style":1267},"language-ts shiki shiki-themes github-light github-dark-dimmed","class A {\n  private b = new B();\n}\n","ts","",[1222,1269,1270,1286,1308],{"__ignoreMap":1267},[1271,1272,1274,1278,1282],"span",{"class":1273,"line":340},"line",[1271,1275,1277],{"class":1276},"s7YZ4","class",[1271,1279,1281],{"class":1280},"sOLd2"," A",[1271,1283,1285],{"class":1284},"sYgZi"," {\n",[1271,1287,1288,1291,1295,1298,1301,1305],{"class":1273,"line":329},[1271,1289,1290],{"class":1276},"  private",[1271,1292,1294],{"class":1293},"stnAF"," b",[1271,1296,1297],{"class":1276}," =",[1271,1299,1300],{"class":1276}," new",[1271,1302,1304],{"class":1303},"sPO5f"," B",[1271,1306,1307],{"class":1284},"();\n",[1271,1309,1310],{"class":1273,"line":318},[1271,1311,1312],{"class":1284},"}\n",[1216,1314,1315,1316,1318,1319,1321],{},"這樣做代表 ",[1222,1317,1249],{}," 必須知道 ",[1222,1320,1253],{}," 要怎麼建立，兩個 class 之間的耦合也會比較高。",[1216,1323,1324,1325,1327],{},"另一種方式，是直接把 ",[1222,1326,1253],{}," 的實例傳進來。",[1262,1329,1331],{"className":1264,"code":1330,"language":1266,"meta":1267,"style":1267},"class A {\n  constructor(private b: B) {}\n}\n",[1222,1332,1333,1341,1362],{"__ignoreMap":1267},[1271,1334,1335,1337,1339],{"class":1273,"line":340},[1271,1336,1277],{"class":1276},[1271,1338,1281],{"class":1280},[1271,1340,1285],{"class":1284},[1271,1342,1343,1346,1349,1352,1354,1357,1359],{"class":1273,"line":329},[1271,1344,1345],{"class":1276},"  constructor",[1271,1347,1348],{"class":1284},"(",[1271,1350,1351],{"class":1276},"private",[1271,1353,1294],{"class":1293},[1271,1355,1356],{"class":1276},":",[1271,1358,1304],{"class":1280},[1271,1360,1361],{"class":1284},") {}\n",[1271,1363,1364],{"class":1273,"line":318},[1271,1365,1312],{"class":1284},[1216,1367,1368,1369,1371,1372,1374],{},"這時 ",[1222,1370,1249],{}," 只需要知道自己依賴 ",[1222,1373,1253],{},"，不需要負責它的建立方式。",[1216,1376,1377],{},"當應用程式裡的依賴越來越多，就需要由 DI 系統統一管理，例如依賴如何建立、哪些實例可以共用，以及它們應該存在多久。",[1216,1379,1380],{},"在 Angular 中，這些依賴會交由 Injector 管理。當 Component 或 Service 需要某個依賴時，Angular 會透過 Injector 找到對應的 Provider，再取得或建立需要的實例。",[1237,1382,1384],{"id":1383},"injector-跟-inject","Injector 跟 inject()",[1216,1386,1387,1388,1390],{},"Injector 和 ",[1222,1389,1224],{}," 名稱很像，但代表不同的概念。",[1216,1392,1393],{},"Injector 是 DI 系統中負責管理與提供依賴的角色。它會根據註冊的 Provider，決定依賴要如何取得，以及對應實例的作用範圍與生命週期。",[1216,1395,1396,1397,1400],{},"像常見的 ",[1222,1398,1399],{},"providedIn: 'root'","，就是把 Service 提供在應用程式的 root Injector 中。其他地方需要這個 Service 時，Angular 就能透過對應的 Provider 取得或建立實例。",[1216,1402,1403,1405],{},[1222,1404,1224],{}," 則是一個函式，用來向目前的 Injector 取得依賴。",[1262,1407,1409],{"className":1264,"code":1408,"language":1266,"meta":1267,"style":1267},"private readonly userService = inject(UserService);\n",[1222,1410,1411],{"__ignoreMap":1267},[1271,1412,1413,1416,1419,1422],{"class":1273,"line":340},[1271,1414,1415],{"class":1284},"private readonly userService ",[1271,1417,1418],{"class":1276},"=",[1271,1420,1421],{"class":1303}," inject",[1271,1423,1424],{"class":1284},"(UserService);\n",[1216,1426,1427,1428,1431,1432,1435],{},"執行 ",[1222,1429,1430],{},"inject(UserService)"," 時，Angular 會根據目前的 Injection Context 找到可用的 Injector，再透過對應的 Provider 取得或建立 ",[1222,1433,1434],{},"UserService"," 實例。",[1216,1437,1438,1439,1441],{},"不過 ",[1222,1440,1224],{}," 不能在任何地方直接呼叫。它必須在 Injection Context 中執行，Angular 才知道目前要使用哪一個 Injector。",[1216,1443,1444],{},[1445,1446],"img",{"alt":1447,"src":1448},"Angular DI：依賴是怎麼取得的？","https:\u002F\u002Fres.cloudinary.com\u002Fdseg0uwc9\u002Fimage\u002Fupload\u002Fv1790651336\u002F2026%20%E9%90%B5%E4%BA%BA%E8%B3%BD\u002FDay%2015%EF%BC%9A%E6%90%9E%E6%87%82%20Injection%20Context%EF%BC%8C%E5%BE%9E%20inject%28%29%E3%80%81runInInjectionContext%28%29%20%E5%88%B0%20Reactive%20Context\u002Fangular-di-resolution-flow.png",[1237,1450,1452],{"id":1451},"哪些地方本身就有-injection-context","哪些地方本身就有 Injection Context",[1216,1454,1455],{},"Injection Context 可以理解成「Angular 知道目前要使用哪個 Injector」的執行環境。",[1216,1457,1458,1459,1461],{},"當 Angular 正在建立由 DI 系統管理的實例，例如 Component、Directive、Service 或 Pipe，就會提供這個執行環境，因此可以直接使用 ",[1222,1460,1224],{},"。",[1216,1463,1464],{},"例如：",[1262,1466,1468],{"className":1264,"code":1467,"language":1266,"meta":1267,"style":1267},"@Injectable({\n  providedIn: 'root',\n})\nexport class UserService {\n  private readonly http = inject(HttpClient);\n}\n",[1222,1469,1470,1481,1493,1498,1511,1528],{"__ignoreMap":1267},[1271,1471,1472,1475,1478],{"class":1273,"line":340},[1271,1473,1474],{"class":1284},"@",[1271,1476,1477],{"class":1303},"Injectable",[1271,1479,1480],{"class":1284},"({\n",[1271,1482,1483,1486,1490],{"class":1273,"line":329},[1271,1484,1485],{"class":1284},"  providedIn: ",[1271,1487,1489],{"class":1488},"s-HuK","'root'",[1271,1491,1492],{"class":1284},",\n",[1271,1494,1495],{"class":1273,"line":318},[1271,1496,1497],{"class":1284},"})\n",[1271,1499,1500,1503,1506,1509],{"class":1273,"line":134},[1271,1501,1502],{"class":1276},"export",[1271,1504,1505],{"class":1276}," class",[1271,1507,1508],{"class":1280}," UserService",[1271,1510,1285],{"class":1284},[1271,1512,1513,1515,1518,1521,1523,1525],{"class":1273,"line":122},[1271,1514,1290],{"class":1276},[1271,1516,1517],{"class":1276}," readonly",[1271,1519,1520],{"class":1293}," http",[1271,1522,1297],{"class":1276},[1271,1524,1421],{"class":1303},[1271,1526,1527],{"class":1284},"(HttpClient);\n",[1271,1529,1530],{"class":1273,"line":31},[1271,1531,1312],{"class":1284},[1216,1533,1534,1535,1538,1539,1541],{},"這裡的 ",[1222,1536,1537],{},"inject(HttpClient)"," 可以正常執行，是因為欄位初始化發生在 Angular 建立 ",[1222,1540,1434],{}," 的過程中。",[1216,1543,1544],{},"Component 也是一樣：",[1262,1546,1548],{"className":1264,"code":1547,"language":1266,"meta":1267,"style":1267},"@Component({\n  selector: 'app-user',\n  template: `...`,\n})\nexport class UserComponent {\n  private readonly userService = inject(UserService);\n}\n",[1222,1549,1550,1559,1569,1579,1583,1594,1609],{"__ignoreMap":1267},[1271,1551,1552,1554,1557],{"class":1273,"line":340},[1271,1553,1474],{"class":1284},[1271,1555,1556],{"class":1303},"Component",[1271,1558,1480],{"class":1284},[1271,1560,1561,1564,1567],{"class":1273,"line":329},[1271,1562,1563],{"class":1284},"  selector: ",[1271,1565,1566],{"class":1488},"'app-user'",[1271,1568,1492],{"class":1284},[1271,1570,1571,1574,1577],{"class":1273,"line":318},[1271,1572,1573],{"class":1284},"  template: ",[1271,1575,1576],{"class":1488},"`...`",[1271,1578,1492],{"class":1284},[1271,1580,1581],{"class":1273,"line":134},[1271,1582,1497],{"class":1284},[1271,1584,1585,1587,1589,1592],{"class":1273,"line":122},[1271,1586,1502],{"class":1276},[1271,1588,1505],{"class":1276},[1271,1590,1591],{"class":1280}," UserComponent",[1271,1593,1285],{"class":1284},[1271,1595,1596,1598,1600,1603,1605,1607],{"class":1273,"line":31},[1271,1597,1290],{"class":1276},[1271,1599,1517],{"class":1276},[1271,1601,1602],{"class":1293}," userService",[1271,1604,1297],{"class":1276},[1271,1606,1421],{"class":1303},[1271,1608,1424],{"class":1284},[1271,1610,1611],{"class":1273,"line":17},[1271,1612,1312],{"class":1284},[1216,1614,1615],{},"constructor 執行期間也位在 Injection Context 中：",[1262,1617,1619],{"className":1264,"code":1618,"language":1266,"meta":1267,"style":1267},"export class UserComponent {\n  constructor() {\n    const userService = inject(UserService);\n  }\n}\n",[1222,1620,1621,1631,1638,1652,1657],{"__ignoreMap":1267},[1271,1622,1623,1625,1627,1629],{"class":1273,"line":340},[1271,1624,1502],{"class":1276},[1271,1626,1505],{"class":1276},[1271,1628,1591],{"class":1280},[1271,1630,1285],{"class":1284},[1271,1632,1633,1635],{"class":1273,"line":329},[1271,1634,1345],{"class":1276},[1271,1636,1637],{"class":1284},"() {\n",[1271,1639,1640,1643,1646,1648,1650],{"class":1273,"line":318},[1271,1641,1642],{"class":1276},"    const",[1271,1644,1602],{"class":1645},"sviXB",[1271,1647,1297],{"class":1276},[1271,1649,1421],{"class":1303},[1271,1651,1424],{"class":1284},[1271,1653,1654],{"class":1273,"line":134},[1271,1655,1656],{"class":1284},"  }\n",[1271,1658,1659],{"class":1273,"line":122},[1271,1660,1312],{"class":1284},[1216,1662,1663,1664,1461],{},"Provider 的 factory 同樣是在 Angular 的 DI 流程中執行，因此也能使用 ",[1222,1665,1224],{},[1262,1667,1669],{"className":1264,"code":1668,"language":1266,"meta":1267,"style":1267},"{\n  provide: API_URL,\n  useFactory: () => {\n    const config = inject(ConfigService);\n\n    return config.apiUrl;\n  },\n}\n",[1222,1670,1671,1676,1689,1702,1716,1722,1730,1735],{"__ignoreMap":1267},[1271,1672,1673],{"class":1273,"line":340},[1271,1674,1675],{"class":1284},"{\n",[1271,1677,1678,1681,1684,1687],{"class":1273,"line":329},[1271,1679,1680],{"class":1280},"  provide",[1271,1682,1683],{"class":1284},": ",[1271,1685,1686],{"class":1645},"API_URL",[1271,1688,1492],{"class":1284},[1271,1690,1691,1694,1697,1700],{"class":1273,"line":318},[1271,1692,1693],{"class":1280},"  useFactory",[1271,1695,1696],{"class":1284},": () ",[1271,1698,1699],{"class":1276},"=>",[1271,1701,1285],{"class":1284},[1271,1703,1704,1706,1709,1711,1713],{"class":1273,"line":134},[1271,1705,1642],{"class":1276},[1271,1707,1708],{"class":1645}," config",[1271,1710,1297],{"class":1276},[1271,1712,1421],{"class":1303},[1271,1714,1715],{"class":1284},"(ConfigService);\n",[1271,1717,1718],{"class":1273,"line":122},[1271,1719,1721],{"emptyLinePlaceholder":1720},true,"\n",[1271,1723,1724,1727],{"class":1273,"line":31},[1271,1725,1726],{"class":1276},"    return",[1271,1728,1729],{"class":1284}," config.apiUrl;\n",[1271,1731,1732],{"class":1273,"line":17},[1271,1733,1734],{"class":1284},"  },\n",[1271,1736,1737],{"class":1273,"line":110},[1271,1738,1312],{"class":1284},[1216,1740,1741,1742,1744],{},"這些情況的共同點，是 ",[1222,1743,1224],{}," 執行時，Angular 正處於可用的 DI 執行環境中。",[1237,1746,1748],{"id":1747},"哪些地方沒有-injection-context","哪些地方沒有 Injection Context",[1216,1750,1751],{},"離開 DI 建立流程後，就不一定還存在 Injection Context。",[1216,1753,1754,1755,1757],{},"例如把 ",[1222,1756,1224],{}," 放在一般 method 中：",[1262,1759,1761],{"className":1264,"code":1760,"language":1266,"meta":1267,"style":1267},"export class UserComponent {\n  loadUser() {\n    const userService = inject(UserService);\n  }\n}\n",[1222,1762,1763,1773,1780,1792,1796],{"__ignoreMap":1267},[1271,1764,1765,1767,1769,1771],{"class":1273,"line":340},[1271,1766,1502],{"class":1276},[1271,1768,1505],{"class":1276},[1271,1770,1591],{"class":1280},[1271,1772,1285],{"class":1284},[1271,1774,1775,1778],{"class":1273,"line":329},[1271,1776,1777],{"class":1303},"  loadUser",[1271,1779,1637],{"class":1284},[1271,1781,1782,1784,1786,1788,1790],{"class":1273,"line":318},[1271,1783,1642],{"class":1276},[1271,1785,1602],{"class":1645},[1271,1787,1297],{"class":1276},[1271,1789,1421],{"class":1303},[1271,1791,1424],{"class":1284},[1271,1793,1794],{"class":1273,"line":134},[1271,1795,1656],{"class":1284},[1271,1797,1798],{"class":1273,"line":122},[1271,1799,1312],{"class":1284},[1216,1801,1802,1805],{},[1222,1803,1804],{},"loadUser()"," 可能是在使用者點擊按鈕後才被呼叫：",[1262,1807,1811],{"className":1808,"code":1809,"language":1810,"meta":1267,"style":1267},"language-html shiki shiki-themes github-light github-dark-dimmed","\u003Cbutton (click)=\"loadUser()\">\n  Load User\n\u003C\u002Fbutton>\n","html",[1222,1812,1813,1834,1839],{"__ignoreMap":1267},[1271,1814,1815,1818,1822,1826,1828,1831],{"class":1273,"line":340},[1271,1816,1817],{"class":1284},"\u003C",[1271,1819,1821],{"class":1820},"sIAta","button",[1271,1823,1825],{"class":1824},"sMOND"," (click)",[1271,1827,1418],{"class":1284},[1271,1829,1830],{"class":1488},"\"loadUser()\"",[1271,1832,1833],{"class":1284},">\n",[1271,1835,1836],{"class":1273,"line":329},[1271,1837,1838],{"class":1284},"  Load User\n",[1271,1840,1841,1844,1846],{"class":1273,"line":318},[1271,1842,1843],{"class":1284},"\u003C\u002F",[1271,1845,1821],{"class":1820},[1271,1847,1833],{"class":1284},[1216,1849,1850,1851,1853],{},"這時 Component 已經建立完成，",[1222,1852,1804],{}," 只是一般的 method 呼叫，不能再依賴建立 Component 時的 Injection Context。",[1216,1855,1856],{},"callback 也會遇到相同情況：",[1262,1858,1860],{"className":1264,"code":1859,"language":1266,"meta":1267,"style":1267},"setTimeout(() => {\n  const userService = inject(UserService);\n});\n",[1222,1861,1862,1874,1887],{"__ignoreMap":1267},[1271,1863,1864,1867,1870,1872],{"class":1273,"line":340},[1271,1865,1866],{"class":1303},"setTimeout",[1271,1868,1869],{"class":1284},"(() ",[1271,1871,1699],{"class":1276},[1271,1873,1285],{"class":1284},[1271,1875,1876,1879,1881,1883,1885],{"class":1273,"line":329},[1271,1877,1878],{"class":1276},"  const",[1271,1880,1602],{"class":1645},[1271,1882,1297],{"class":1276},[1271,1884,1421],{"class":1303},[1271,1886,1424],{"class":1284},[1271,1888,1889],{"class":1273,"line":318},[1271,1890,1891],{"class":1284},"});\n",[1216,1893,1894],{},"等到 callback 真正執行時，也已經離開原本的 DI 流程。",[1216,1896,1897,1898,1461],{},"因此 Injection Context 不會跟著 class 或實例持續存在。即使這個 class 是由 Angular 建立，也不代表裡面的所有 method 或 callback 都能直接呼叫 ",[1222,1899,1224],{},[1237,1901,1903],{"id":1902},"runininjectioncontext-是拿來做什麼","runInInjectionContext() 是拿來做什麼",[1216,1905,1906,1907,1909,1910,1461],{},"如果目前不在 Injection Context 中，但需要執行會使用 ",[1222,1908,1224],{}," 的程式碼，就可以使用 ",[1222,1911,1228],{},[1216,1913,1914],{},"可以先在有 Injection Context 的地方取得目前的 Injector，例如 Component 的欄位初始化階段：",[1262,1916,1918],{"className":1264,"code":1917,"language":1266,"meta":1267,"style":1267},"@Component({\n  selector: 'app-user',\n  template: `\n    \u003Cbutton (click)=\"loadUser()\">Load User\u003C\u002Fbutton>\n  `,\n})\nexport class UserComponent {\n  private readonly injector = inject(Injector);\n\n  loadUser() {\n    runInInjectionContext(this.injector, () => {\n      const userService = inject(UserService);\n\n      userService.load();\n    });\n  }\n}\n",[1222,1919,1920,1928,1936,1943,1948,1955,1959,1969,1985,1989,1995,2011,2024,2028,2038,2043,2047],{"__ignoreMap":1267},[1271,1921,1922,1924,1926],{"class":1273,"line":340},[1271,1923,1474],{"class":1284},[1271,1925,1556],{"class":1303},[1271,1927,1480],{"class":1284},[1271,1929,1930,1932,1934],{"class":1273,"line":329},[1271,1931,1563],{"class":1284},[1271,1933,1566],{"class":1488},[1271,1935,1492],{"class":1284},[1271,1937,1938,1940],{"class":1273,"line":318},[1271,1939,1573],{"class":1284},[1271,1941,1942],{"class":1488},"`\n",[1271,1944,1945],{"class":1273,"line":134},[1271,1946,1947],{"class":1488},"    \u003Cbutton (click)=\"loadUser()\">Load User\u003C\u002Fbutton>\n",[1271,1949,1950,1953],{"class":1273,"line":122},[1271,1951,1952],{"class":1488},"  `",[1271,1954,1492],{"class":1284},[1271,1956,1957],{"class":1273,"line":31},[1271,1958,1497],{"class":1284},[1271,1960,1961,1963,1965,1967],{"class":1273,"line":17},[1271,1962,1502],{"class":1276},[1271,1964,1505],{"class":1276},[1271,1966,1591],{"class":1280},[1271,1968,1285],{"class":1284},[1271,1970,1971,1973,1975,1978,1980,1982],{"class":1273,"line":110},[1271,1972,1290],{"class":1276},[1271,1974,1517],{"class":1276},[1271,1976,1977],{"class":1293}," injector",[1271,1979,1297],{"class":1276},[1271,1981,1421],{"class":1303},[1271,1983,1984],{"class":1284},"(Injector);\n",[1271,1986,1987],{"class":1273,"line":76},[1271,1988,1721],{"emptyLinePlaceholder":1720},[1271,1990,1991,1993],{"class":1273,"line":247},[1271,1992,1777],{"class":1303},[1271,1994,1637],{"class":1284},[1271,1996,1997,2000,2002,2004,2007,2009],{"class":1273,"line":236},[1271,1998,1999],{"class":1303},"    runInInjectionContext",[1271,2001,1348],{"class":1284},[1271,2003,1128],{"class":1645},[1271,2005,2006],{"class":1284},".injector, () ",[1271,2008,1699],{"class":1276},[1271,2010,1285],{"class":1284},[1271,2012,2013,2016,2018,2020,2022],{"class":1273,"line":225},[1271,2014,2015],{"class":1276},"      const",[1271,2017,1602],{"class":1645},[1271,2019,1297],{"class":1276},[1271,2021,1421],{"class":1303},[1271,2023,1424],{"class":1284},[1271,2025,2026],{"class":1273,"line":214},[1271,2027,1721],{"emptyLinePlaceholder":1720},[1271,2029,2030,2033,2036],{"class":1273,"line":203},[1271,2031,2032],{"class":1284},"      userService.",[1271,2034,2035],{"class":1303},"load",[1271,2037,1307],{"class":1284},[1271,2039,2040],{"class":1273,"line":192},[1271,2041,2042],{"class":1284},"    });\n",[1271,2044,2045],{"class":1273,"line":181},[1271,2046,1656],{"class":1284},[1271,2048,2049],{"class":1273,"line":170},[1271,2050,1312],{"class":1284},[1216,2052,2053,2056],{},[1222,2054,2055],{},"inject(Injector)"," 執行在 Component 的欄位初始化階段，因此可以取得目前的 Injector。",[1216,2058,2059,2060,2062,2063,2065,2066,2068],{},"等到之後執行 ",[1222,2061,1804],{}," 時，雖然已經離開原本的 Injection Context，仍然可以把先前取得的 Injector 傳給 ",[1222,2064,1228],{},"，讓 callback 內的 ",[1222,2067,1430],{}," 正常解析依賴。",[1216,2070,2071,2073],{},[1222,2072,1228],{}," 不會建立新的 DI 系統，而是讓 callback 暫時在指定的 Injection Context 中執行。",[1216,2075,2076],{},"不過這個 Context 只存在於同步執行期間。",[1262,2078,2080],{"className":1264,"code":2079,"language":1266,"meta":1267,"style":1267},"runInInjectionContext(this.injector, async () => {\n  const userService = inject(UserService);\n\n  await fetch('\u002Fapi\u002Fusers');\n\n  \u002F\u002F await 之後不能再依賴原本的 Injection Context\n});\n",[1222,2081,2082,2104,2116,2120,2136,2140,2146],{"__ignoreMap":1267},[1271,2083,2084,2087,2089,2091,2094,2097,2100,2102],{"class":1273,"line":340},[1271,2085,2086],{"class":1303},"runInInjectionContext",[1271,2088,1348],{"class":1284},[1271,2090,1128],{"class":1645},[1271,2092,2093],{"class":1284},".injector, ",[1271,2095,2096],{"class":1276},"async",[1271,2098,2099],{"class":1284}," () ",[1271,2101,1699],{"class":1276},[1271,2103,1285],{"class":1284},[1271,2105,2106,2108,2110,2112,2114],{"class":1273,"line":329},[1271,2107,1878],{"class":1276},[1271,2109,1602],{"class":1645},[1271,2111,1297],{"class":1276},[1271,2113,1421],{"class":1303},[1271,2115,1424],{"class":1284},[1271,2117,2118],{"class":1273,"line":318},[1271,2119,1721],{"emptyLinePlaceholder":1720},[1271,2121,2122,2125,2128,2130,2133],{"class":1273,"line":134},[1271,2123,2124],{"class":1276},"  await",[1271,2126,2127],{"class":1303}," fetch",[1271,2129,1348],{"class":1284},[1271,2131,2132],{"class":1488},"'\u002Fapi\u002Fusers'",[1271,2134,2135],{"class":1284},");\n",[1271,2137,2138],{"class":1273,"line":122},[1271,2139,1721],{"emptyLinePlaceholder":1720},[1271,2141,2142],{"class":1273,"line":31},[1271,2143,2145],{"class":2144},"sDN9O","  \u002F\u002F await 之後不能再依賴原本的 Injection Context\n",[1271,2147,2148],{"class":1273,"line":17},[1271,2149,1891],{"class":1284},[1216,2151,2152,2153,2156,2157,2159],{},"經過 ",[1222,2154,2155],{},"await"," 後，後續程式碼已經離開原本的同步執行區段。如果後面還需要使用某個 Service，可以先在 ",[1222,2158,2155],{}," 前取得實例：",[1262,2161,2163],{"className":1264,"code":2162,"language":1266,"meta":1267,"style":1267},"runInInjectionContext(this.injector, async () => {\n  const userService = inject(UserService);\n\n  await fetch('\u002Fapi\u002Fusers');\n\n  userService.refresh();\n});\n",[1222,2164,2165,2183,2195,2199,2211,2215,2225],{"__ignoreMap":1267},[1271,2166,2167,2169,2171,2173,2175,2177,2179,2181],{"class":1273,"line":340},[1271,2168,2086],{"class":1303},[1271,2170,1348],{"class":1284},[1271,2172,1128],{"class":1645},[1271,2174,2093],{"class":1284},[1271,2176,2096],{"class":1276},[1271,2178,2099],{"class":1284},[1271,2180,1699],{"class":1276},[1271,2182,1285],{"class":1284},[1271,2184,2185,2187,2189,2191,2193],{"class":1273,"line":329},[1271,2186,1878],{"class":1276},[1271,2188,1602],{"class":1645},[1271,2190,1297],{"class":1276},[1271,2192,1421],{"class":1303},[1271,2194,1424],{"class":1284},[1271,2196,2197],{"class":1273,"line":318},[1271,2198,1721],{"emptyLinePlaceholder":1720},[1271,2200,2201,2203,2205,2207,2209],{"class":1273,"line":134},[1271,2202,2124],{"class":1276},[1271,2204,2127],{"class":1303},[1271,2206,1348],{"class":1284},[1271,2208,2132],{"class":1488},[1271,2210,2135],{"class":1284},[1271,2212,2213],{"class":1273,"line":122},[1271,2214,1721],{"emptyLinePlaceholder":1720},[1271,2216,2217,2220,2223],{"class":1273,"line":31},[1271,2218,2219],{"class":1284},"  userService.",[1271,2221,2222],{"class":1303},"refresh",[1271,2224,1307],{"class":1284},[1271,2226,2227],{"class":1273,"line":17},[1271,2228,1891],{"class":1284},[1216,2230,2231,2232,2234,2235,2238,2239,1461],{},"這裡 ",[1222,2233,2155],{}," 之後使用的是前面已經取得的 ",[1222,2236,2237],{},"userService","，而不是再次呼叫 ",[1222,2240,1224],{},[1216,2242,2243],{},[1445,2244],{"alt":2245,"src":2246},"Injection Context 只在同步執行期間有效","https:\u002F\u002Fres.cloudinary.com\u002Fdseg0uwc9\u002Fimage\u002Fupload\u002Fv1790653260\u002F2026%20%E9%90%B5%E4%BA%BA%E8%B3%BD\u002FDay%2015%EF%BC%9A%E6%90%9E%E6%87%82%20Injection%20Context%EF%BC%8C%E5%BE%9E%20inject%28%29%E3%80%81runInInjectionContext%28%29%20%E5%88%B0%20Reactive%20Context\u002Finjection-context-execution-window-v2.png",[1237,2248,2250],{"id":2249},"runininjectioncontext-跟-injectasync-的差別","runInInjectionContext() 跟 injectAsync() 的差別",[1216,2252,2253,2254,2256,2257,2260,2261,2263,2264,2266],{},"前面提到，",[1222,2255,1228],{}," 提供的 Injection Context 只存在於同步執行期間。這時可能會想到前一篇介紹過的 ",[1222,2258,2259],{},"injectAsync()","：既然 Injection Context 不能跨過 ",[1222,2262,2155],{},"，為什麼 ",[1222,2265,2259],{}," 可以等到之後才取得 Service？",[1216,2268,2269],{},"兩者處理的是不同問題。",[1216,2271,2272,2274,2275,1461],{},[1222,2273,1228],{}," 是指定一個 Injector，讓 callback 在執行期間可以使用 ",[1222,2276,1224],{},[1262,2278,2280],{"className":1264,"code":2279,"language":1266,"meta":1267,"style":1267},"runInInjectionContext(this.injector, () => {\n  const userService = inject(UserService);\n});\n",[1222,2281,2282,2296,2308],{"__ignoreMap":1267},[1271,2283,2284,2286,2288,2290,2292,2294],{"class":1273,"line":340},[1271,2285,2086],{"class":1303},[1271,2287,1348],{"class":1284},[1271,2289,1128],{"class":1645},[1271,2291,2006],{"class":1284},[1271,2293,1699],{"class":1276},[1271,2295,1285],{"class":1284},[1271,2297,2298,2300,2302,2304,2306],{"class":1273,"line":329},[1271,2299,1878],{"class":1276},[1271,2301,1602],{"class":1645},[1271,2303,1297],{"class":1276},[1271,2305,1421],{"class":1303},[1271,2307,1424],{"class":1284},[1271,2309,2310],{"class":1273,"line":318},[1271,2311,1891],{"class":1284},[1216,2313,2314,2316],{},[1222,2315,2259],{}," 的做法不同。它通常會在 Component 或 Service 建立時執行，而這個階段本來就位在 Injection Context 中，因此可以先取得目前的 Injector。",[1262,2318,2320],{"className":1264,"code":2319,"language":1266,"meta":1267,"style":1267},"private readonly userService = injectAsync(\n  () =>\n    import('.\u002Fuser.service')\n      .then(m => m.UserService)\n);\n",[1222,2321,2322,2334,2342,2355,2374],{"__ignoreMap":1267},[1271,2323,2324,2326,2328,2331],{"class":1273,"line":340},[1271,2325,1415],{"class":1284},[1271,2327,1418],{"class":1276},[1271,2329,2330],{"class":1303}," injectAsync",[1271,2332,2333],{"class":1284},"(\n",[1271,2335,2336,2339],{"class":1273,"line":329},[1271,2337,2338],{"class":1284},"  () ",[1271,2340,2341],{"class":1276},"=>\n",[1271,2343,2344,2347,2349,2352],{"class":1273,"line":318},[1271,2345,2346],{"class":1276},"    import",[1271,2348,1348],{"class":1284},[1271,2350,2351],{"class":1488},"'.\u002Fuser.service'",[1271,2353,2354],{"class":1284},")\n",[1271,2356,2357,2360,2363,2365,2368,2371],{"class":1273,"line":134},[1271,2358,2359],{"class":1284},"      .",[1271,2361,2362],{"class":1303},"then",[1271,2364,1348],{"class":1284},[1271,2366,2367],{"class":1293},"m",[1271,2369,2370],{"class":1276}," =>",[1271,2372,2373],{"class":1284}," m.UserService)\n",[1271,2375,2376],{"class":1273,"line":122},[1271,2377,2135],{"class":1284},[1216,2379,2380],{},"之後即使從一般 method 中呼叫：",[1262,2382,2384],{"className":1264,"code":2383,"language":1266,"meta":1267,"style":1267},"async loadUser() {\n  const userService = await this.userService();\n\n  userService.load();\n}\n",[1222,2385,2386,2396,2417,2421,2429],{"__ignoreMap":1267},[1271,2387,2388,2391,2394],{"class":1273,"line":340},[1271,2389,2390],{"class":1284},"async ",[1271,2392,2393],{"class":1303},"loadUser",[1271,2395,1637],{"class":1284},[1271,2397,2398,2400,2402,2404,2407,2410,2413,2415],{"class":1273,"line":329},[1271,2399,1878],{"class":1276},[1271,2401,1602],{"class":1645},[1271,2403,1297],{"class":1276},[1271,2405,2406],{"class":1276}," await",[1271,2408,2409],{"class":1645}," this",[1271,2411,2412],{"class":1284},".",[1271,2414,2237],{"class":1303},[1271,2416,1307],{"class":1284},[1271,2418,2419],{"class":1273,"line":318},[1271,2420,1721],{"emptyLinePlaceholder":1720},[1271,2422,2423,2425,2427],{"class":1273,"line":134},[1271,2424,2219],{"class":1284},[1271,2426,2035],{"class":1303},[1271,2428,1307],{"class":1284},[1271,2430,2431],{"class":1273,"line":122},[1271,2432,1312],{"class":1284},[1216,2434,2435,2436,2438],{},"這時已經不一定還有 Injection Context，但 ",[1222,2437,2259],{}," 不需要重新尋找 Injector，因為建立時就已經先取得了。",[1216,2440,2441,2442,2445],{},"真正呼叫 ",[1222,2443,2444],{},"this.userService()"," 後，才會執行 loader：",[1262,2447,2449],{"className":1264,"code":2448,"language":1266,"meta":1267,"style":1267},"() =>\n  import('.\u002Fuser.service')\n    .then(m => m.UserService)\n",[1222,2450,2451,2458,2469],{"__ignoreMap":1267},[1271,2452,2453,2456],{"class":1273,"line":340},[1271,2454,2455],{"class":1284},"() ",[1271,2457,2341],{"class":1276},[1271,2459,2460,2463,2465,2467],{"class":1273,"line":329},[1271,2461,2462],{"class":1276},"  import",[1271,2464,1348],{"class":1284},[1271,2466,2351],{"class":1488},[1271,2468,2354],{"class":1284},[1271,2470,2471,2474,2476,2478,2480,2482],{"class":1273,"line":318},[1271,2472,2473],{"class":1284},"    .",[1271,2475,2362],{"class":1303},[1271,2477,1348],{"class":1284},[1271,2479,2367],{"class":1293},[1271,2481,2370],{"class":1276},[1271,2483,2373],{"class":1284},[1216,2485,2486,2487,2489],{},"載入完成後取得 ",[1222,2488,1434],{}," 這個 Provider Token，再透過先前取得的 Injector 解析對應實例。",[1216,2491,2492],{},"因此：",[1262,2494,2496],{"className":1264,"code":2495,"language":1266,"meta":1267,"style":1267},"const userService = await this.userService();\n",[1222,2497,2498],{"__ignoreMap":1267},[1271,2499,2500,2502,2504,2506,2508,2510,2512,2514],{"class":1273,"line":340},[1271,2501,1029],{"class":1276},[1271,2503,1602],{"class":1645},[1271,2505,1297],{"class":1276},[1271,2507,2406],{"class":1276},[1271,2509,2409],{"class":1645},[1271,2511,2412],{"class":1284},[1271,2513,2237],{"class":1303},[1271,2515,1307],{"class":1284},[1216,2517,1534,2518,2520],{},[1222,2519,2155],{}," 是在等待 Service 完成載入與 DI 解析，不是把原本的 Injection Context 延續到非同步流程之後。",[1216,2522,2523],{},"兩個 API 可以這樣區分：",[2525,2526,2527,2538],"ul",{},[2528,2529,2530,2535,2536,1461],"li",{},[2531,2532,2533],"strong",{},[1222,2534,1228],{},"：指定 Injector，讓同步 callback 可以使用 ",[1222,2537,1224],{},[2528,2539,2540,2544],{},[2531,2541,2542],{},[1222,2543,2259],{},"：建立時取得 Injector，真正使用時再非同步載入並解析依賴。",[1216,2546,2547,2548,2550,2551,2553],{},"所以 ",[1222,2549,2259],{}," 不是非同步版的 ",[1222,2552,1228],{},"。兩者都會使用 Injector，但使用方式與時機不同。",[1216,2555,2556],{},[1445,2557],{"alt":2558,"src":2559},"runInInjectionContext() vs injectAsync()","https:\u002F\u002Fres.cloudinary.com\u002Fdseg0uwc9\u002Fimage\u002Fupload\u002Fv1790735918\u002F2026%20%E9%90%B5%E4%BA%BA%E8%B3%BD\u002FDay%2015%EF%BC%9A%E6%90%9E%E6%87%82%20Injection%20Context%EF%BC%8C%E5%BE%9E%20inject%28%29%E3%80%81runInInjectionContext%28%29%20%E5%88%B0%20Reactive%20Context\u002Frun-in-injection-context-vs-inject-async.png",[1216,2561,2562,2563,2566],{},"前一篇提到的 ",[1222,2564,2565],{},"prefetch"," 也不會改變這件事。",[1262,2568,2570],{"className":1264,"code":2569,"language":1266,"meta":1267,"style":1267},"private readonly userService = injectAsync(\n  () =>\n    import('.\u002Fuser.service')\n      .then(m => m.UserService),\n  {\n    prefetch: onIdle,\n  }\n);\n",[1222,2571,2572,2582,2588,2598,2613,2618,2623,2627],{"__ignoreMap":1267},[1271,2573,2574,2576,2578,2580],{"class":1273,"line":340},[1271,2575,1415],{"class":1284},[1271,2577,1418],{"class":1276},[1271,2579,2330],{"class":1303},[1271,2581,2333],{"class":1284},[1271,2583,2584,2586],{"class":1273,"line":329},[1271,2585,2338],{"class":1284},[1271,2587,2341],{"class":1276},[1271,2589,2590,2592,2594,2596],{"class":1273,"line":318},[1271,2591,2346],{"class":1276},[1271,2593,1348],{"class":1284},[1271,2595,2351],{"class":1488},[1271,2597,2354],{"class":1284},[1271,2599,2600,2602,2604,2606,2608,2610],{"class":1273,"line":134},[1271,2601,2359],{"class":1284},[1271,2603,2362],{"class":1303},[1271,2605,1348],{"class":1284},[1271,2607,2367],{"class":1293},[1271,2609,2370],{"class":1276},[1271,2611,2612],{"class":1284}," m.UserService),\n",[1271,2614,2615],{"class":1273,"line":122},[1271,2616,2617],{"class":1284},"  {\n",[1271,2619,2620],{"class":1273,"line":31},[1271,2621,2622],{"class":1284},"    prefetch: onIdle,\n",[1271,2624,2625],{"class":1273,"line":17},[1271,2626,1656],{"class":1284},[1271,2628,2629],{"class":1273,"line":110},[1271,2630,2135],{"class":1284},[1216,2632,2633,2636,2637,2639],{},[1222,2634,2635],{},"prefetch: onIdle"," 只影響 loader 什麼時候開始載入。瀏覽器進入 Idle 後可以先載入對應的程式碼，而 ",[1222,2638,2259],{}," 使用哪個 Injector，仍然是在建立時決定。",[1237,2641,2643],{"id":2642},"tosignal-為什麼也需要-injection-context","toSignal() 為什麼也需要 Injection Context",[1216,2645,2646,2647,1461],{},"Injection Context 的限制不只會出現在 ",[1222,2648,1224],{},[1216,2650,2651,2652,2655],{},"前面介紹 Signal 時常用到的 ",[1222,2653,2654],{},"toSignal()","，預設也需要在 Injection Context 中執行。",[1216,2657,2658],{},"例如放在 Component 的欄位初始化階段：",[1262,2660,2662],{"className":1264,"code":2661,"language":1266,"meta":1267,"style":1267},"@Component({\n  selector: 'app-user',\n  template: `\n    @if (user(); as user) {\n      \u003Cp>{{ user.name }}\u003C\u002Fp>\n    }\n  `,\n})\nexport class UserComponent {\n  private readonly userService = inject(UserService);\n\n  readonly user = toSignal(\n    this.userService.getUser()\n  );\n}\n",[1222,2663,2664,2672,2680,2686,2691,2696,2701,2707,2711,2721,2735,2739,2754,2768,2773],{"__ignoreMap":1267},[1271,2665,2666,2668,2670],{"class":1273,"line":340},[1271,2667,1474],{"class":1284},[1271,2669,1556],{"class":1303},[1271,2671,1480],{"class":1284},[1271,2673,2674,2676,2678],{"class":1273,"line":329},[1271,2675,1563],{"class":1284},[1271,2677,1566],{"class":1488},[1271,2679,1492],{"class":1284},[1271,2681,2682,2684],{"class":1273,"line":318},[1271,2683,1573],{"class":1284},[1271,2685,1942],{"class":1488},[1271,2687,2688],{"class":1273,"line":134},[1271,2689,2690],{"class":1488},"    @if (user(); as user) {\n",[1271,2692,2693],{"class":1273,"line":122},[1271,2694,2695],{"class":1488},"      \u003Cp>{{ user.name }}\u003C\u002Fp>\n",[1271,2697,2698],{"class":1273,"line":31},[1271,2699,2700],{"class":1488},"    }\n",[1271,2702,2703,2705],{"class":1273,"line":17},[1271,2704,1952],{"class":1488},[1271,2706,1492],{"class":1284},[1271,2708,2709],{"class":1273,"line":110},[1271,2710,1497],{"class":1284},[1271,2712,2713,2715,2717,2719],{"class":1273,"line":76},[1271,2714,1502],{"class":1276},[1271,2716,1505],{"class":1276},[1271,2718,1591],{"class":1280},[1271,2720,1285],{"class":1284},[1271,2722,2723,2725,2727,2729,2731,2733],{"class":1273,"line":247},[1271,2724,1290],{"class":1276},[1271,2726,1517],{"class":1276},[1271,2728,1602],{"class":1293},[1271,2730,1297],{"class":1276},[1271,2732,1421],{"class":1303},[1271,2734,1424],{"class":1284},[1271,2736,2737],{"class":1273,"line":236},[1271,2738,1721],{"emptyLinePlaceholder":1720},[1271,2740,2741,2744,2747,2749,2752],{"class":1273,"line":225},[1271,2742,2743],{"class":1276},"  readonly",[1271,2745,2746],{"class":1293}," user",[1271,2748,1297],{"class":1276},[1271,2750,2751],{"class":1303}," toSignal",[1271,2753,2333],{"class":1284},[1271,2755,2756,2759,2762,2765],{"class":1273,"line":214},[1271,2757,2758],{"class":1645},"    this",[1271,2760,2761],{"class":1284},".userService.",[1271,2763,2764],{"class":1303},"getUser",[1271,2766,2767],{"class":1284},"()\n",[1271,2769,2770],{"class":1273,"line":203},[1271,2771,2772],{"class":1284},"  );\n",[1271,2774,2775],{"class":1273,"line":192},[1271,2776,1312],{"class":1284},[1216,2778,1534,2779,2781,2782,2785],{},[1222,2780,2654],{}," 會在 Angular 建立 ",[1222,2783,2784],{},"UserComponent"," 的過程中執行，因此當下本來就位在 Injection Context。",[1216,2787,2788,2790,2791,2794],{},[1222,2789,2654],{}," 會訂閱 Observable，因此也需要處理訂閱的生命週期。它會透過 Injector 取得 ",[1222,2792,2793],{},"DestroyRef","，並把清理邏輯註冊到對應的生命週期上。",[1216,2796,2797,2798,2800],{},"如果是在沒有 Injection Context 的地方呼叫 ",[1222,2799,2654],{},"，可以自行提供 Injector：",[1262,2802,2804],{"className":1264,"code":2803,"language":1266,"meta":1267,"style":1267},"@Component({\n  selector: 'app-user',\n  template: `...`,\n})\nexport class UserComponent {\n  private readonly injector = inject(Injector);\n  private readonly userService = inject(UserService);\n\n  createUserSignal() {\n    return toSignal(\n      this.userService.getUser(),\n      {\n        injector: this.injector,\n      }\n    );\n  }\n}\n",[1222,2805,2806,2814,2822,2830,2834,2844,2858,2872,2876,2883,2891,2903,2908,2918,2923,2928,2932],{"__ignoreMap":1267},[1271,2807,2808,2810,2812],{"class":1273,"line":340},[1271,2809,1474],{"class":1284},[1271,2811,1556],{"class":1303},[1271,2813,1480],{"class":1284},[1271,2815,2816,2818,2820],{"class":1273,"line":329},[1271,2817,1563],{"class":1284},[1271,2819,1566],{"class":1488},[1271,2821,1492],{"class":1284},[1271,2823,2824,2826,2828],{"class":1273,"line":318},[1271,2825,1573],{"class":1284},[1271,2827,1576],{"class":1488},[1271,2829,1492],{"class":1284},[1271,2831,2832],{"class":1273,"line":134},[1271,2833,1497],{"class":1284},[1271,2835,2836,2838,2840,2842],{"class":1273,"line":122},[1271,2837,1502],{"class":1276},[1271,2839,1505],{"class":1276},[1271,2841,1591],{"class":1280},[1271,2843,1285],{"class":1284},[1271,2845,2846,2848,2850,2852,2854,2856],{"class":1273,"line":31},[1271,2847,1290],{"class":1276},[1271,2849,1517],{"class":1276},[1271,2851,1977],{"class":1293},[1271,2853,1297],{"class":1276},[1271,2855,1421],{"class":1303},[1271,2857,1984],{"class":1284},[1271,2859,2860,2862,2864,2866,2868,2870],{"class":1273,"line":17},[1271,2861,1290],{"class":1276},[1271,2863,1517],{"class":1276},[1271,2865,1602],{"class":1293},[1271,2867,1297],{"class":1276},[1271,2869,1421],{"class":1303},[1271,2871,1424],{"class":1284},[1271,2873,2874],{"class":1273,"line":110},[1271,2875,1721],{"emptyLinePlaceholder":1720},[1271,2877,2878,2881],{"class":1273,"line":76},[1271,2879,2880],{"class":1303},"  createUserSignal",[1271,2882,1637],{"class":1284},[1271,2884,2885,2887,2889],{"class":1273,"line":247},[1271,2886,1726],{"class":1276},[1271,2888,2751],{"class":1303},[1271,2890,2333],{"class":1284},[1271,2892,2893,2896,2898,2900],{"class":1273,"line":236},[1271,2894,2895],{"class":1645},"      this",[1271,2897,2761],{"class":1284},[1271,2899,2764],{"class":1303},[1271,2901,2902],{"class":1284},"(),\n",[1271,2904,2905],{"class":1273,"line":225},[1271,2906,2907],{"class":1284},"      {\n",[1271,2909,2910,2913,2915],{"class":1273,"line":214},[1271,2911,2912],{"class":1284},"        injector: ",[1271,2914,1128],{"class":1645},[1271,2916,2917],{"class":1284},".injector,\n",[1271,2919,2920],{"class":1273,"line":203},[1271,2921,2922],{"class":1284},"      }\n",[1271,2924,2925],{"class":1273,"line":192},[1271,2926,2927],{"class":1284},"    );\n",[1271,2929,2930],{"class":1273,"line":181},[1271,2931,1656],{"class":1284},[1271,2933,2934],{"class":1273,"line":170},[1271,2935,1312],{"class":1284},[1216,2937,1368,2938,2940,2941,2943],{},[1222,2939,2654],{}," 會使用傳入的 Injector 取得 ",[1222,2942,2793],{},"，不需要依賴呼叫當下的 Injection Context。",[1216,2945,2946,2947,2949],{},"清理時機會和傳入的 Injector 對應生命週期有關。假設使用的是 Component 所在的 Injector，Component 被銷毀時，",[1222,2948,2654],{}," 建立的訂閱也會一起清理；如果使用更高層級的 Injector，對應的生命週期也會更長。",[1216,2951,2952,2953,2955,2956,2958,2959,2961],{},"因此 ",[1222,2954,2654],{}," 並不是自己知道它屬於哪個 Component，而是透過 Injector 取得對應的 ",[1222,2957,2793],{},"，再由 ",[1222,2960,2793],{}," 處理生命週期的清理。",[1237,2963,2965],{"id":2964},"injection-context-跟-reactive-context-的差別","Injection Context 跟 Reactive Context 的差別",[1216,2967,2968],{},"Reactive Context 前面已經介紹過，這裡簡單和 Injection Context 做區分：",[2525,2970,2971,2980],{},[2528,2972,2973,2976,2977,2979],{},[2531,2974,2975],{},"Injection Context"," 關心的是「現在要從哪個 Injector 取得依賴」，主要和 DI、",[1222,2978,1224],{},"、生命週期有關。",[2528,2981,2982,2985],{},[2531,2983,2984],{},"Reactive Context"," 關心的是「現在讀取了哪些 Signal」，主要用來建立並追蹤 Signal 之間的依賴關係。",[1216,2987,2988],{},[1445,2989],{"alt":2990,"src":2991},"Injection Context vs Reactive Context","https:\u002F\u002Fres.cloudinary.com\u002Fdseg0uwc9\u002Fimage\u002Fupload\u002Fv1790649773\u002F2026%20%E9%90%B5%E4%BA%BA%E8%B3%BD\u002FDay%2015%EF%BC%9A%E6%90%9E%E6%87%82%20Injection%20Context%EF%BC%8C%E5%BE%9E%20inject%28%29%E3%80%81runInInjectionContext%28%29%20%E5%88%B0%20Reactive%20Context\u002Finjection-context-vs-reactive-context.png",[1237,2993,2994],{"id":2994},"本日結語",[1216,2996,2997,2999],{},[1222,2998,1228],{}," 的作用，是在 callback 執行期間暫時指定目前要使用的 Injector。callback 結束後，Angular 會還原原本的狀態，因此這個 Injection Context 只存在於同步執行期間。",[1216,3001,3002,3003,3005,3006,3008],{},"遇到 ",[1222,3004,2155],{}," 後，原本的同步執行區段已經結束，後續程式碼不能再依賴同一個 Injection Context 呼叫 ",[1222,3007,1224],{},"。如果後面還需要使用某個依賴，可以先取得實例，或保留 Injector 再交給需要它的 API。",[1216,3010,3011,3012,3015,3016,3019],{},"Reactive Context 也有類似的概念。",[1222,3013,3014],{},"computed()"," 或 ",[1222,3017,3018],{},"effect()"," 執行時，Angular 會記錄目前是哪個 Consumer 正在讀取 Signal，用來建立依賴關係。Injection Context 處理的是依賴從哪個 Injector 取得，Reactive Context 處理的則是 Signal 之間的依賴追蹤。",[1216,3021,3022,3023,3025,3026,3029],{},"實務上可以把依賴盡量放在建立階段取得，後續直接使用已經取得的實例或 Injector。需要在其他執行時機建立 Injection Context 時，再使用 ",[1222,3024,1228],{}," 或 API 提供的 ",[1222,3027,3028],{},"injector"," 選項。",[3031,3032,3033],"h3",{"id":3033},"資料來源",[2525,3035,3036,3049,3062,3076,3090],{},[2528,3037,3038,3045,3046,3048],{},[3039,3040,3044],"a",{"href":3041,"rel":3042},"https:\u002F\u002Fangular.dev\u002Fguide\u002Fdi\u002Fdependency-injection-context",[3043],"nofollow","Angular 官方文件：Injection context","：哪些地方存在 Injection Context，以及 ",[1222,3047,1228],{}," 的用法。",[2528,3050,3051,3056,3057,3059,3060,1461],{},[3039,3052,3055],{"href":3053,"rel":3054},"https:\u002F\u002Fangular.dev\u002Fecosystem\u002Frxjs-interop#injection-context",[3043],"Angular RxJS interop 官方文件：Injection context","：",[1222,3058,2654],{}," 預設需要 Injection Context，也可以改傳 ",[1222,3061,3028],{},[2528,3063,3064,3056,3069,3071,3072,3075],{},[3039,3065,3068],{"href":3066,"rel":3067},"https:\u002F\u002Fgithub.com\u002Fangular\u002Fangular\u002Fblob\u002Fmain\u002Fpackages\u002Fcore\u002Fsrc\u002Fdi\u002Fcontextual.ts",[3043],"Angular 原始碼：contextual.ts",[1222,3070,1228],{}," 執行 callback 前設定目前的 Injector，結束後在 ",[1222,3073,3074],{},"finally"," 還原。",[2528,3077,3078,3056,3083,3085,3086,3089],{},[3039,3079,3082],{"href":3080,"rel":3081},"https:\u002F\u002Fgithub.com\u002Fangular\u002Fangular\u002Fblob\u002Fmain\u002Fpackages\u002Fcore\u002Fsrc\u002Fdi\u002Finject_async.ts",[3043],"Angular 原始碼：inject_async.ts",[1222,3084,2259],{}," 建立時就取得 ",[1222,3087,3088],{},"Injector","，載入完成後再用它解析依賴。",[2528,3091,3092,3097,3098,3100,3101,3103],{},[3039,3093,3096],{"href":3094,"rel":3095},"https:\u002F\u002Fgithub.com\u002Fangular\u002Fangular\u002Fblob\u002Fmain\u002Fpackages\u002Fcore\u002Frxjs-interop\u002Fsrc\u002Fto_signal.ts",[3043],"Angular 原始碼：to_signal.ts","：有傳 ",[1222,3099,3028],{}," 時從它取得 ",[1222,3102,2793],{},"，否則從目前的 Injection Context 取得。",[3105,3106,3107],"style",{},"html pre.shiki code .s7YZ4, html code.shiki .s7YZ4{--shiki-default:#D73A49;--shiki-dark:#F47067}html pre.shiki code .sOLd2, html code.shiki .sOLd2{--shiki-default:#6F42C1;--shiki-dark:#F69D50}html pre.shiki code .sYgZi, html code.shiki .sYgZi{--shiki-default:#24292E;--shiki-dark:#ADBAC7}html pre.shiki code .stnAF, html code.shiki .stnAF{--shiki-default:#E36209;--shiki-dark:#F69D50}html pre.shiki code .sPO5f, html code.shiki .sPO5f{--shiki-default:#6F42C1;--shiki-dark:#DCBDFB}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 .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 .sIAta, html code.shiki .sIAta{--shiki-default:#22863A;--shiki-dark:#8DDB8C}html pre.shiki code .sMOND, html code.shiki .sMOND{--shiki-default:#6F42C1;--shiki-dark:#6CB6FF}html pre.shiki code .sDN9O, html code.shiki .sDN9O{--shiki-default:#6A737D;--shiki-dark:#768390}",{"title":1267,"searchDepth":134,"depth":134,"links":3109},[3110,3111,3112,3113,3114,3115,3116,3117,3118],{"id":1239,"depth":329,"text":1240},{"id":1383,"depth":329,"text":1384},{"id":1451,"depth":329,"text":1452},{"id":1747,"depth":329,"text":1748},{"id":1902,"depth":329,"text":1903},{"id":2249,"depth":329,"text":2250},{"id":2642,"depth":329,"text":2643},{"id":2964,"depth":329,"text":2965},{"id":2994,"depth":329,"text":2994,"children":3119},[3120],{"id":3033,"depth":318,"text":3033},[11,13],"md",{},"---\ntitle: \"Day 15：搞懂 Injection Context，從 inject()、runInInjectionContext() 到 injectAsync()\"\ndate: 2026-09-29 13:44:28\ntags:\n  - \"iThome 鐵人賽\"\n  - \"2026 鐵人賽\"\n  - \"Angular\"\ncategories:\n  - \"iThome 鐵人賽\"\n  - \"Angular\"\ndescription: \"前面提到 Injection Context 時，可能會讓人聯想到先前介紹過的 Reactive Context。我一開始也有點搞混，因此花了一些時間重新理解 Angular 裡這些不同的執行環境。\"\ncanonical: https:\u002F\u002Fithelp.ithome.com.tw\u002Farticles\u002F10418752\nseries:\n  name: \"2026 iThome 鐵人賽：Angular 22 Signal 進化論\"\n  url: https:\u002F\u002Fithelp.ithome.com.tw\u002Fusers\u002F20116554\u002Fironman\u002F9939\n  day: 15\n---\n\n前面提到 Injection Context 時，可能會讓人聯想到先前介紹過的 Reactive Context。我一開始也有點搞混，因此花了一些時間重新理解 Angular 裡這些不同的執行環境。\n\n平常使用 Angular 提供的 API 時，我們不一定會注意它們需要在哪個 Context 中執行。直到遇到 `inject()`、`runInInjectionContext()` 這類 API，才會發現執行環境會直接影響函式能不能正常使用。\n\n之前同事也曾經問過我，`runInInjectionContext()` 到底是拿來做什麼的。這篇就從這個問題開始，整理 Injection Context 的用途，以及它和 Reactive Context 的差別。\n\n## Angular DI 系統\n\nAngular 本身建立在一套 DI（Dependency Injection，依賴注入）系統上。\n\n假設 `A` class 需要使用 `B` class，最直接的做法是在 `A` 裡自行建立 `B` 的實例。\n\n```ts\nclass A {\n  private b = new B();\n}\n```\n\n這樣做代表 `A` 必須知道 `B` 要怎麼建立，兩個 class 之間的耦合也會比較高。\n\n另一種方式，是直接把 `B` 的實例傳進來。\n\n```ts\nclass A {\n  constructor(private b: B) {}\n}\n```\n\n這時 `A` 只需要知道自己依賴 `B`，不需要負責它的建立方式。\n\n當應用程式裡的依賴越來越多，就需要由 DI 系統統一管理，例如依賴如何建立、哪些實例可以共用，以及它們應該存在多久。\n\n在 Angular 中，這些依賴會交由 Injector 管理。當 Component 或 Service 需要某個依賴時，Angular 會透過 Injector 找到對應的 Provider，再取得或建立需要的實例。\n\n## Injector 跟 inject()\n\nInjector 和 `inject()` 名稱很像，但代表不同的概念。\n\nInjector 是 DI 系統中負責管理與提供依賴的角色。它會根據註冊的 Provider，決定依賴要如何取得，以及對應實例的作用範圍與生命週期。\n\n像常見的 `providedIn: 'root'`，就是把 Service 提供在應用程式的 root Injector 中。其他地方需要這個 Service 時，Angular 就能透過對應的 Provider 取得或建立實例。\n\n`inject()` 則是一個函式，用來向目前的 Injector 取得依賴。\n\n```ts\nprivate readonly userService = inject(UserService);\n```\n\n執行 `inject(UserService)` 時，Angular 會根據目前的 Injection Context 找到可用的 Injector，再透過對應的 Provider 取得或建立 `UserService` 實例。\n\n不過 `inject()` 不能在任何地方直接呼叫。它必須在 Injection Context 中執行，Angular 才知道目前要使用哪一個 Injector。\n\n![Angular DI：依賴是怎麼取得的？](https:\u002F\u002Fres.cloudinary.com\u002Fdseg0uwc9\u002Fimage\u002Fupload\u002Fv1790651336\u002F2026%20%E9%90%B5%E4%BA%BA%E8%B3%BD\u002FDay%2015%EF%BC%9A%E6%90%9E%E6%87%82%20Injection%20Context%EF%BC%8C%E5%BE%9E%20inject%28%29%E3%80%81runInInjectionContext%28%29%20%E5%88%B0%20Reactive%20Context\u002Fangular-di-resolution-flow.png)\n\n## 哪些地方本身就有 Injection Context\n\nInjection Context 可以理解成「Angular 知道目前要使用哪個 Injector」的執行環境。\n\n當 Angular 正在建立由 DI 系統管理的實例，例如 Component、Directive、Service 或 Pipe，就會提供這個執行環境，因此可以直接使用 `inject()`。\n\n例如：\n\n```ts\n@Injectable({\n  providedIn: 'root',\n})\nexport class UserService {\n  private readonly http = inject(HttpClient);\n}\n```\n\n這裡的 `inject(HttpClient)` 可以正常執行，是因為欄位初始化發生在 Angular 建立 `UserService` 的過程中。\n\nComponent 也是一樣：\n\n```ts\n@Component({\n  selector: 'app-user',\n  template: `...`,\n})\nexport class UserComponent {\n  private readonly userService = inject(UserService);\n}\n```\n\nconstructor 執行期間也位在 Injection Context 中：\n\n```ts\nexport class UserComponent {\n  constructor() {\n    const userService = inject(UserService);\n  }\n}\n```\n\nProvider 的 factory 同樣是在 Angular 的 DI 流程中執行，因此也能使用 `inject()`。\n\n```ts\n{\n  provide: API_URL,\n  useFactory: () => {\n    const config = inject(ConfigService);\n\n    return config.apiUrl;\n  },\n}\n```\n\n這些情況的共同點，是 `inject()` 執行時，Angular 正處於可用的 DI 執行環境中。\n\n## 哪些地方沒有 Injection Context\n\n離開 DI 建立流程後，就不一定還存在 Injection Context。\n\n例如把 `inject()` 放在一般 method 中：\n\n```ts\nexport class UserComponent {\n  loadUser() {\n    const userService = inject(UserService);\n  }\n}\n```\n\n`loadUser()` 可能是在使用者點擊按鈕後才被呼叫：\n\n```html\n\u003Cbutton (click)=\"loadUser()\">\n  Load User\n\u003C\u002Fbutton>\n```\n\n這時 Component 已經建立完成，`loadUser()` 只是一般的 method 呼叫，不能再依賴建立 Component 時的 Injection Context。\n\ncallback 也會遇到相同情況：\n\n```ts\nsetTimeout(() => {\n  const userService = inject(UserService);\n});\n```\n\n等到 callback 真正執行時，也已經離開原本的 DI 流程。\n\n因此 Injection Context 不會跟著 class 或實例持續存在。即使這個 class 是由 Angular 建立，也不代表裡面的所有 method 或 callback 都能直接呼叫 `inject()`。\n\n## runInInjectionContext() 是拿來做什麼\n\n如果目前不在 Injection Context 中，但需要執行會使用 `inject()` 的程式碼，就可以使用 `runInInjectionContext()`。\n\n可以先在有 Injection Context 的地方取得目前的 Injector，例如 Component 的欄位初始化階段：\n\n```ts\n@Component({\n  selector: 'app-user',\n  template: `\n    \u003Cbutton (click)=\"loadUser()\">Load User\u003C\u002Fbutton>\n  `,\n})\nexport class UserComponent {\n  private readonly injector = inject(Injector);\n\n  loadUser() {\n    runInInjectionContext(this.injector, () => {\n      const userService = inject(UserService);\n\n      userService.load();\n    });\n  }\n}\n```\n\n`inject(Injector)` 執行在 Component 的欄位初始化階段，因此可以取得目前的 Injector。\n\n等到之後執行 `loadUser()` 時，雖然已經離開原本的 Injection Context，仍然可以把先前取得的 Injector 傳給 `runInInjectionContext()`，讓 callback 內的 `inject(UserService)` 正常解析依賴。\n\n`runInInjectionContext()` 不會建立新的 DI 系統，而是讓 callback 暫時在指定的 Injection Context 中執行。\n\n不過這個 Context 只存在於同步執行期間。\n\n```ts\nrunInInjectionContext(this.injector, async () => {\n  const userService = inject(UserService);\n\n  await fetch('\u002Fapi\u002Fusers');\n\n  \u002F\u002F await 之後不能再依賴原本的 Injection Context\n});\n```\n\n經過 `await` 後，後續程式碼已經離開原本的同步執行區段。如果後面還需要使用某個 Service，可以先在 `await` 前取得實例：\n\n```ts\nrunInInjectionContext(this.injector, async () => {\n  const userService = inject(UserService);\n\n  await fetch('\u002Fapi\u002Fusers');\n\n  userService.refresh();\n});\n```\n\n這裡 `await` 之後使用的是前面已經取得的 `userService`，而不是再次呼叫 `inject()`。\n\n![Injection Context 只在同步執行期間有效](https:\u002F\u002Fres.cloudinary.com\u002Fdseg0uwc9\u002Fimage\u002Fupload\u002Fv1790653260\u002F2026%20%E9%90%B5%E4%BA%BA%E8%B3%BD\u002FDay%2015%EF%BC%9A%E6%90%9E%E6%87%82%20Injection%20Context%EF%BC%8C%E5%BE%9E%20inject%28%29%E3%80%81runInInjectionContext%28%29%20%E5%88%B0%20Reactive%20Context\u002Finjection-context-execution-window-v2.png)\n\n## runInInjectionContext() 跟 injectAsync() 的差別\n\n前面提到，`runInInjectionContext()` 提供的 Injection Context 只存在於同步執行期間。這時可能會想到前一篇介紹過的 `injectAsync()`：既然 Injection Context 不能跨過 `await`，為什麼 `injectAsync()` 可以等到之後才取得 Service？\n\n兩者處理的是不同問題。\n\n`runInInjectionContext()` 是指定一個 Injector，讓 callback 在執行期間可以使用 `inject()`。\n\n```ts\nrunInInjectionContext(this.injector, () => {\n  const userService = inject(UserService);\n});\n```\n\n`injectAsync()` 的做法不同。它通常會在 Component 或 Service 建立時執行，而這個階段本來就位在 Injection Context 中，因此可以先取得目前的 Injector。\n\n```ts\nprivate readonly userService = injectAsync(\n  () =>\n    import('.\u002Fuser.service')\n      .then(m => m.UserService)\n);\n```\n\n之後即使從一般 method 中呼叫：\n\n```ts\nasync loadUser() {\n  const userService = await this.userService();\n\n  userService.load();\n}\n```\n\n這時已經不一定還有 Injection Context，但 `injectAsync()` 不需要重新尋找 Injector，因為建立時就已經先取得了。\n\n真正呼叫 `this.userService()` 後，才會執行 loader：\n\n```ts\n() =>\n  import('.\u002Fuser.service')\n    .then(m => m.UserService)\n```\n\n載入完成後取得 `UserService` 這個 Provider Token，再透過先前取得的 Injector 解析對應實例。\n\n因此：\n\n```ts\nconst userService = await this.userService();\n```\n\n這裡的 `await` 是在等待 Service 完成載入與 DI 解析，不是把原本的 Injection Context 延續到非同步流程之後。\n\n兩個 API 可以這樣區分：\n\n- **`runInInjectionContext()`**：指定 Injector，讓同步 callback 可以使用 `inject()`。\n- **`injectAsync()`**：建立時取得 Injector，真正使用時再非同步載入並解析依賴。\n\n所以 `injectAsync()` 不是非同步版的 `runInInjectionContext()`。兩者都會使用 Injector，但使用方式與時機不同。\n\n![runInInjectionContext() vs injectAsync()](https:\u002F\u002Fres.cloudinary.com\u002Fdseg0uwc9\u002Fimage\u002Fupload\u002Fv1790735918\u002F2026%20%E9%90%B5%E4%BA%BA%E8%B3%BD\u002FDay%2015%EF%BC%9A%E6%90%9E%E6%87%82%20Injection%20Context%EF%BC%8C%E5%BE%9E%20inject%28%29%E3%80%81runInInjectionContext%28%29%20%E5%88%B0%20Reactive%20Context\u002Frun-in-injection-context-vs-inject-async.png)\n\n前一篇提到的 `prefetch` 也不會改變這件事。\n\n```ts\nprivate readonly userService = injectAsync(\n  () =>\n    import('.\u002Fuser.service')\n      .then(m => m.UserService),\n  {\n    prefetch: onIdle,\n  }\n);\n```\n\n`prefetch: onIdle` 只影響 loader 什麼時候開始載入。瀏覽器進入 Idle 後可以先載入對應的程式碼，而 `injectAsync()` 使用哪個 Injector，仍然是在建立時決定。\n\n## toSignal() 為什麼也需要 Injection Context\n\nInjection Context 的限制不只會出現在 `inject()`。\n\n前面介紹 Signal 時常用到的 `toSignal()`，預設也需要在 Injection Context 中執行。\n\n例如放在 Component 的欄位初始化階段：\n\n```ts\n@Component({\n  selector: 'app-user',\n  template: `\n    @if (user(); as user) {\n      \u003Cp>{{ user.name }}\u003C\u002Fp>\n    }\n  `,\n})\nexport class UserComponent {\n  private readonly userService = inject(UserService);\n\n  readonly user = toSignal(\n    this.userService.getUser()\n  );\n}\n```\n\n這裡的 `toSignal()` 會在 Angular 建立 `UserComponent` 的過程中執行，因此當下本來就位在 Injection Context。\n\n`toSignal()` 會訂閱 Observable，因此也需要處理訂閱的生命週期。它會透過 Injector 取得 `DestroyRef`，並把清理邏輯註冊到對應的生命週期上。\n\n如果是在沒有 Injection Context 的地方呼叫 `toSignal()`，可以自行提供 Injector：\n\n```ts\n@Component({\n  selector: 'app-user',\n  template: `...`,\n})\nexport class UserComponent {\n  private readonly injector = inject(Injector);\n  private readonly userService = inject(UserService);\n\n  createUserSignal() {\n    return toSignal(\n      this.userService.getUser(),\n      {\n        injector: this.injector,\n      }\n    );\n  }\n}\n```\n\n這時 `toSignal()` 會使用傳入的 Injector 取得 `DestroyRef`，不需要依賴呼叫當下的 Injection Context。\n\n清理時機會和傳入的 Injector 對應生命週期有關。假設使用的是 Component 所在的 Injector，Component 被銷毀時，`toSignal()` 建立的訂閱也會一起清理；如果使用更高層級的 Injector，對應的生命週期也會更長。\n\n因此 `toSignal()` 並不是自己知道它屬於哪個 Component，而是透過 Injector 取得對應的 `DestroyRef`，再由 `DestroyRef` 處理生命週期的清理。\n\n## Injection Context 跟 Reactive Context 的差別\n\nReactive Context 前面已經介紹過，這裡簡單和 Injection Context 做區分：\n\n- **Injection Context** 關心的是「現在要從哪個 Injector 取得依賴」，主要和 DI、`inject()`、生命週期有關。\n- **Reactive Context** 關心的是「現在讀取了哪些 Signal」，主要用來建立並追蹤 Signal 之間的依賴關係。\n\n![Injection Context vs Reactive Context](https:\u002F\u002Fres.cloudinary.com\u002Fdseg0uwc9\u002Fimage\u002Fupload\u002Fv1790649773\u002F2026%20%E9%90%B5%E4%BA%BA%E8%B3%BD\u002FDay%2015%EF%BC%9A%E6%90%9E%E6%87%82%20Injection%20Context%EF%BC%8C%E5%BE%9E%20inject%28%29%E3%80%81runInInjectionContext%28%29%20%E5%88%B0%20Reactive%20Context\u002Finjection-context-vs-reactive-context.png)\n\n## 本日結語\n\n`runInInjectionContext()` 的作用，是在 callback 執行期間暫時指定目前要使用的 Injector。callback 結束後，Angular 會還原原本的狀態，因此這個 Injection Context 只存在於同步執行期間。\n\n遇到 `await` 後，原本的同步執行區段已經結束，後續程式碼不能再依賴同一個 Injection Context 呼叫 `inject()`。如果後面還需要使用某個依賴，可以先取得實例，或保留 Injector 再交給需要它的 API。\n\nReactive Context 也有類似的概念。`computed()` 或 `effect()` 執行時，Angular 會記錄目前是哪個 Consumer 正在讀取 Signal，用來建立依賴關係。Injection Context 處理的是依賴從哪個 Injector 取得，Reactive Context 處理的則是 Signal 之間的依賴追蹤。\n\n實務上可以把依賴盡量放在建立階段取得，後續直接使用已經取得的實例或 Injector。需要在其他執行時機建立 Injection Context 時，再使用 `runInInjectionContext()` 或 API 提供的 `injector` 選項。\n\n### 資料來源\n\n- [Angular 官方文件：Injection context](https:\u002F\u002Fangular.dev\u002Fguide\u002Fdi\u002Fdependency-injection-context)：哪些地方存在 Injection Context，以及 `runInInjectionContext()` 的用法。\n- [Angular RxJS interop 官方文件：Injection context](https:\u002F\u002Fangular.dev\u002Fecosystem\u002Frxjs-interop#injection-context)：`toSignal()` 預設需要 Injection Context，也可以改傳 `injector`。\n- [Angular 原始碼：contextual.ts](https:\u002F\u002Fgithub.com\u002Fangular\u002Fangular\u002Fblob\u002Fmain\u002Fpackages\u002Fcore\u002Fsrc\u002Fdi\u002Fcontextual.ts)：`runInInjectionContext()` 執行 callback 前設定目前的 Injector，結束後在 `finally` 還原。\n- [Angular 原始碼：inject\\_async.ts](https:\u002F\u002Fgithub.com\u002Fangular\u002Fangular\u002Fblob\u002Fmain\u002Fpackages\u002Fcore\u002Fsrc\u002Fdi\u002Finject_async.ts)：`injectAsync()` 建立時就取得 `Injector`，載入完成後再用它解析依賴。\n- [Angular 原始碼：to\\_signal.ts](https:\u002F\u002Fgithub.com\u002Fangular\u002Fangular\u002Fblob\u002Fmain\u002Fpackages\u002Fcore\u002Frxjs-interop\u002Fsrc\u002Fto_signal.ts)：有傳 `injector` 時從它取得 `DestroyRef`，否則從目前的 Injection Context 取得。\n",{"title":184,"description":185},{"name":20,"url":21,"day":192},{"loc":183,"images":3128,"lastmod":186},[3129,3130,3131,3132],{"loc":1448},{"loc":2246},{"loc":2559},{"loc":2991},"ithome-2026-day-15","2026-09-29-ithome-2026-day-15",[11,12,13],"8qsvN7KoA9QkaPjjGWin6EFQkkFs9OUd6aKsKsNM9kE",1792575176548]