WebWorkers problem in Angular related to Vite `optimizeDeps`
- 主要语言
- TypeScript
- 星标
- 27k
- 派生
- 11.8k
- 平均合并
- 14 小时 23 分钟
- 30 天内合并 PR
- 162
描述
### Command
serve
### Is this a regression?
- [ ] Yes, this behavior used to work in the previous version
### The previous version in which this bug was not present was
_No response_
### Description
We have a [library](https://github.com/cornerstonejs/cornerstone3D/) that utilizes web workers. It employs [the new Worker interface](https://github.com/cornerstonejs/cornerstone3D/blob/main/packages/dicomImageLoader/src/init.ts#L7-L11):
```js
const instance = new Worker(
new URL('./decodeImageFrameWorker.js', import.meta.url),
{ type: 'module' }
);
```
We have successfully consumed the lib in various scenarios, whether based on Webpack or Vite. See the examples below:
- https://github.com/cornerstonejs/vite-react-cornerstone3d
- https://github.com/cornerstonejs/vue-cornerstone3d
- https://github.com/cornerstonejs/nextjs-cornerstone3d
When integrating into a Vite-based framework, a warning appears regarding one of the dependencies. [This is a known issue in Vite](https://github.com/vitejs/vite/issues/8427), specifically with esbuild. To resolve this, we should add the library to `optimizeDeps` in the Vite config - recommended by vite maintainers, which works well.
I attempted to [integrate a poc of the same library](https://github.com/cornerstonejs/angular-cornerstone3d) in Angular and encountered a similar warning. I tried customizing Vite but faced a limitation, as there is no way to override `optimizeDeps` in Angular, as noted [here](https://github.com/angular/angular-cli/issues/26859).

In some threads, I see that setting
```
"cli": {
"cache": {
"enabled": false
}
}
```
removes the warning above, but then the worker is requested from an incorrect path.

I also have tried the following
```js
"development": {
"buildTarget": "angular-vite-6:build:development",
"prebundle": false
}
```
still no success
### Minimal Reproduction
This is basically minimal repo for reproduction
- https://github.com/cornerstonejs/angular-cornerstone3d
commands to run
```
npm i
npm run start
```
### Exception or Error
```text
With the cache enabled, the Vite warning appears, and disabling the cache loads the worker from the wrong path.
```
### Your Environment
```text
Angular CLI: 19.0.2
Node: 18.19.1
Package Manager: npm 10.2.4
OS: darwin arm64
Angular: 19.0.1
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1900.2
@angular-devkit/build-angular 19.0.2
@angular-devkit/core 19.0.2
@angular-devkit/schematics 19.0.2
@angular/cli 19.0.2
@schematics/angular 19.0.2
rxjs 7.8.1
typescript 5.6.3
zone.js 0.15.0
```
### Anything else relevant?
I want to emphasize that other Vite-based implementations for [Vue](https://github.com/cornerstonejs/vue-cornerstone3d), [React](https://github.com/cornerstonejs/vite-react-cornerstone3d), and [Quasar](https://github.com/sedghi/quasar-cornerstone3D) work, so it's only Angular that's not working.
In addition, the `npm run build` also does not work and tries to load the worker from a wrong path (Again the build with vite, and webpack works)

贡献指南
调研方向
Clone the linked cornerstonejs/angular-cornerstone3d reproduction and run npm i followed by npm run start; compare its Angular setup with the working Vite examples. Investigate Angular CLI handling of Vite optimizeDeps, caching, and module workers, then verify that the warning is resolved, the worker uses the correct path, and npm run build succeeds.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- typescript, vite
- 领域
- build-system, tooling
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 42/100