chore(loader-client,loader-server): package.json entry points name files the build does not produce

未关闭 适合新手
#144 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
78/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
bun, typescript
领域
build-system

调研方向

阅读 apps/client/package.json 和 apps/server/package.json,并同时查看生成其 dist 文件的构建配置。运行 pnpm build,并将输出与声明的 main、module、types、exports 和 browser 字段进行比较。更新入口点元数据,使其与构建生成的文件相匹配,保留 CLI 使用的 ./package.json 导出,并验证两个包都能按预期解析。

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

描述

app:client app:server bug chore good first issue
Which app is this bug report for?

other

Issue description

Applies to client and server.

main, module, types and exports point to dist/index.{cjs,js,d.cts,d.ts} (client package.json#L19-L34, server package.json#L19-L34). The build only writes dist/server.js (plus dist/worker.js for the server):

$ pnpm build && ls apps/client/dist apps/server/dist
apps/client/dist: server.js
apps/server/dist: server.js worker.js

Both packages also declare "browser": true, though they are Bun servers. Anything that resolves the package entry fails; the CLI only works because it resolves package.json and runs the start script.

Suggested fix: remove the dead entry fields and browser (or point them at dist/server.js). Keep the ./package.json export, which the CLI uses.

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

Code sample

No response

Versions
  • @nanoforge-dev/loader-client / @nanoforge-dev/loader-server / @nanoforge-dev/loader-website 1.7.0 (main @ 044c766)
  • Bun 1.3.14
  • Linux x86_64
Issue priority

Low (slightly annoying)

I have tested this issue on a development release

044c766

主要语言
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 摘要。