Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

worker starting further workers

未关闭
#12 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
javascript
领域
web-dev

调研方向

先阅读 node.js,并跟踪 require('web-worker') 如何在父进程和子进程中调用 workerThread。复现 issue 中描述的嵌套 worker 情况,并验证消息是否只传递一次,然后确定拆分 node.js 是否足以支持启动更多 worker 的 worker。

由索引模型根据 Issue 内容生成。

描述

I recently ran into a bad trap: I had another require('web-worker') in the code of the child and not only in the parent. This doesn't work, because the workerThread function is then executed again. The symptom is that messages are received twice in the worker.

This was hard to figure out. Note that this is not really a user's error, because a web worker is normally allowed to start another web worker. So it makes sense in general. (In my code, I could simply comment the bad require out, though.)

I guess that you need to split node.js into two files for this, because the main/worker dichotomy doesn't work anymore when workers can start workers.

主要语言
JavaScript
星标
1.2k
派生
57
PR 合并指标
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

developit/web-worker 的其他 Issue

查看 developit/web-worker 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。