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

web: a fizzy.js to embed fizzy on a page's canvas, without patching globals

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
javascript, wasm, zig
领域
frontend, web-dev

调研方向

Start by reading web/index.html and dvui's web.js to trace how imports, event listeners, plugins, and rendering are handled. The issue proposes a new fizzy.js module and changes to the web build API, but points to a separate build API issue for part of the scope. Done means callers can embed Fizzy on a canvas with scoped imports and listeners that destroy() removes, while index.html delegates to the module and no longer patches the global WebAssembly API.

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

描述

enhancement

Feature request from Graphl, which embeds fizzy's wasm on a canvas inside someone else's page. An iframe isn't an option for its users.

Today web/index.html:

  • builds the fizzy and env imports inline
  • monkeypatches the global WebAssembly.instantiateStreaming, which changes every wasm instantiation on the host page
  • adds keydown, message, focus and resize listeners on window, and fullscreenchange on document, which take the host page's shortcuts

So Graphl carries its own copy of the 12 imports.

Proposal:

  1. In dvui's web.js, let callers pass extra import namespaces: dvui(canvas, url, { imports }).
  2. Add a fizzy.js module, startFizzy({ canvas, wasm, imports, storage, beforeRun, worker }) → { instance, requestRender, destroy }. It owns the fizzy/env imports, plugin loading and input listeners, scoped to the canvas and removed by destroy().

index.html becomes a thin caller, and the global patch goes. The web build should also let an app add wasm exports and its own page (see the build API issue).

主要语言
Zig
星标
1.5k
派生
40
平均合并
4 小时 39 分钟
30 天内合并 PR
428

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

fizzyedit/fizzy 的其他 Issue

查看 fizzyedit/fizzy 的全部 Issue

相似的 Issue

更多 Web Dev Issue

把新 issue 发到你的邮箱

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