Template tests assume core comes from the monorepo source and fail in a scaffolded workspace
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- node.js, typescript
调研方向
Start with the template Vitest configs and the failing specs named in the report: server/mcp-provider-schemas.spec.ts, server/plugins/identity-sso.spec.ts, and server/actions/connection-permissions.spec.ts. Check how they resolve @agent-native/core and mock paths in both the monorepo and a scaffolded workspace; the report also identifies 94 test files across 13 templates that reference ../packages/core/. Done means the affected template tests pass in a workspace created from packed packages as well as in the monorepo.
由索引模型根据 Issue 内容生成。
描述
Environment: multi-app workspace (chat and dispatch) created with agent-native create, core 0.220.0 installed from npm, apps synced to @agent-native/[email protected] with agent-native template sync, vitest 4.1.12, Node 24.20. The code is unchanged on main at 3a7038f2ea.
What happens: pnpm test in the apps:
chatanddispatch:server/mcp-provider-schemas.spec.tsfails before running any test:FAIL server/mcp-provider-schemas.spec.ts > Chat MCP catalogs Error: Cannot find module '.../apps/chat/actions/hello' imported from .../apps/chat/.generated/actions-registry.tsdispatch: 3 of the 41 tests inserver/plugins/identity-sso.spec.tsfail withTypeError: Cannot read properties of undefined (reading 'headers').dispatch: all 13 tests inserver/actions/connection-permissions.spec.tsfail withrelation "org_members" does not exist.
Why: in the monorepo the templates depend on "@agent-native/core": "workspace:*", so core resolves to packages/core, outside node_modules, and I believe Vitest transforms it like project code. In a scaffolded workspace core lives in node_modules, so Vitest externalizes it and Node loads it directly. Adding test.server.deps.inline: [/@agent-native[\\/]core/] to the app's Vitest config makes the first two failures go away. Then:
loadTemplateMcpConformance(packages/core/src/mcp/provider-schema-conformance.ts:570) loads.generated/actions-registry.tsthrough the default loader, a nativeimport()(:492). The registry imports actions without extensions (../actions/hello), which Node's ESM resolver rejects. Sixteen templates have this spec.identity-sso.spec.tsmocksh3and@agent-native/core/*subpaths. My guess is that, with core externalized, those mocks don't reach the imports made from inside core.connection-permissions.spec.tsmocks../../../../packages/core/dist/db/client.js, a path that only exists in the monorepo. In a workspace the mock never applies and the test reaches a database without the tables.calendar(calendar-mcp-writes.spec.ts) andfactory(operation-executor-priming.spec.ts,operation-executor.core.spec.ts) mock the same kind of path. More broadly,git grepfinds 94 test files in 13 templates that reference../packages/core/paths. I haven't checked them one by one, but any that mocks or imports through such a path should break the same way in a workspace.
Workaround:
- For (1) alone, inline just the loader in the app's
vitest.config.ts; with it, all 15 test files inchatpass:test: { server: { deps: { inline: [ /@agent-native[\\/]core[\\/]dist[\\/](testing|mcp[\\/]provider-schema-conformance)\.js$/, ], }, }, }, - Inlining all of core (
/@agent-native[\\/]core/) also fixes (2). (3) has no config workaround.
Possible fix:
- Have the templates'
vitest.config.tsinline@agent-native/core, so the tests run the same way in the monorepo and in a workspace. - Mock core internals through a path that resolves in both layouts instead of
../../../../packages/core/.... - Running the template tests in a workspace scaffolded from the packed packages would catch this class of bug, along with #8239 (
happy-domresolved only through the monorepo, fixed in #8279).
- 主要语言
- TypeScript
- 星标
- 7.7k
- 派生
- 706
- 平均合并
- 1 天 11 小时
- 30 天内合并 PR
- 790
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
BuilderIO/agent-native 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
BuilderIO/agent-native#9217 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
BuilderIO/agent-native#9124 · 1 条评论 ·
维护者通常 1 天内回复
-
An `absolute` element near the end of a long page gives the toolkit main surface a second scrollbar可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 77/100
BuilderIO/agent-native#8846 · 1 条评论 ·
维护者通常 1 天内回复
-
WebMCP helper fails with “invalid input object” in Chrome 155可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 70/100
BuilderIO/agent-native#8460 · 1 条评论 ·
维护者通常 1 天内回复
-
Skill deletion succeeds but leaves Settings unclickable可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
BuilderIO/agent-native#8109 · 1 条评论 ·
维护者通常 1 天内回复
查看 BuilderIO/agent-native 的全部 Issue
相似的 Issue
-
难度 1/5 1-3 小时 新手友好度 83/100
gofish-graphics/gofish-graphics#1384 ·
维护者通常 1 天内回复
-
adapter bug
难度 2/5 1-3 小时 新手友好度 83/100
Olanetsoft/agent-lookout#353 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
vicharanashala/vibe#1542 ·
维护者通常 1 天内回复
-
bug chore P2 size:XS
难度 2/5 1-3 小时 新手友好度 77/100
josephfung/curia#2666 ·
维护者通常 1 天内回复
-
bug good first issue
难度 2/5 1-3 小时 新手友好度 84/100
devarshishimpi/codra#178 ·
维护者通常 1 天内回复