test: test:e2e fails, and the website, files, manifest and watch code have no tests

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
52/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
领域
testing, tooling

调研方向

Start with the root package.json and turbo.json to trace why pnpm test:e2e has no task, then inspect the existing tests for safe-path and editor-ipc. The issue proposes several possible scopes: define or remove the e2e task, add loader tests for /manifest, /env and /game/*, and add website cache tests. Agree on a scope first; done means the selected tests or script run successfully.

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

描述

enhancement tests
Which app is this feature request for?

other

Feature

pnpm test:e2e (root package.json) fails because no package defines the task, and turbo.json has no test:e2e entry (CI passes e2e-script: ""):

$ pnpm test:e2e
x Could not find task `test:e2e` in project
[ELIFECYCLE] Command failed with exit code 1.
$ pnpm test:unit   ->  Tasks: 2 successful, 2 total  (the website has no test:unit)

Unit tests only cover safe-path (client) and editor-ipc (server). The riskiest code has no test: the env filter (env.ts), files.ts in both apps, manifest hashing, worker spawn and restart, the watchers, and the website cache (cache.ts: hash, size and eviction).

Found during a read-only audit of main @ 044c766 (2026-11-11).

Ideal solution or implementation
  • Either remove test:e2e from the root scripts, or add a minimal e2e: start the client and server loaders on a fixture build, then request /manifest, /env and /game/*.
  • Add unit tests for getGameEnv (client and server), getFiles and updateFiles.
  • Add a test:unit to apps/website for the cache logic.
Alternative solutions or implementations

No response

Other context

Several bugs found in the same audit sit in this untested code (env filtering, worker restart, watchers).

主要语言
TypeScript
星标
1
派生
0
平均合并
17 小时 25 分钟
30 天内合并 PR
11

环境准备

从这里开始

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

NanoForge-dev/Loader 的其他 Issue

查看 NanoForge-dev/Loader 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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