developit / developit/workerize-loader
Breaks on latest gatsby, only when there is a webpack cache
- 主要語言
- JavaScript
- 星號
- 2.3k
- 分支
- 85
- PR 合併指標
- 30 天內沒有已合併 PR
描述
It seems like after I start the Gatsby dev server a second time — and webpack has a cache — the worker doesn't load with the exported worker functions set on the object. The moment I clear webpack's cache and restart the dev server, the worker loads fine again.
Does this very limited description by any chance give you a quick insight about what might be causing this?
I'm afraid I can't really give more details, because the inner workings of gatsby/webpack is just one big black box to me.
I can of course make a minimal reproduction with a newly bootstrapped gatsby, if this would be of any help?
貢獻指南
這個儲存庫沒有索引到貢獻指南
研究方向
使用新初始化的 Gatsby 專案建立最小重現,然後在啟用 webpack 快取的情況下啟動 Gatsby 開發伺服器兩次。比較清除 webpack 快取前後 worker 的載入情況以及匯出的 worker 函式;當 worker 在使用快取重新啟動時能夠連同其匯出的函式一起載入時,即表示完成。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- javascript, webpack
- 領域
- build-system
- Issue 類型
- 缺陷
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 25/100