[Utoopack] utoopack umd 在部分需要 loader 处理的场景会卡死
Open
Nobody has claimed this yet.
S-Bug-confirmed
- Dominant language
- Rust
- Stars
- 2.5k
- Forks
- 128
- Avg merge
- 21h 39m
- Merged PRs (30d)
- 32
Description
What happened?
在 umd 场景下，默认 less 文件会通过 less-loader(*.less -> *.css) -> style-loader(*.css-> *.js) 的处理，目前观察到一些组件库 umd 打包项目会卡死在 turbopack-node 的 nodejs 线程池初始化 -> 进程启动阶段，具体可以看日志:
这个问题比较奇怪，目前在一个简单的带 less 文件的项目中不会复现，本地 link @utoo/pack 依赖调试这个问题不会复现，只有在 npm 版本的 @utoo/pack 会复现。
Expected result
正常 bundle
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the UMD build with a default .less file and the npm-published @utoo/pack, then inspect the turbopack-node Node.js thread-pool initialization where the process stalls; compare it with a locally linked package and a simple less project. Done means the loader chain completes and the UMD bundle is produced normally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, webpack
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100