coze-dev / coze-dev/coze-studio

Windows系统无法正常运行前端frontend工程

Open
#1,784 13 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
21.6k
Forks
3.1k
PR merge metrics
No merged PRs in 30d

Description

前端工程frontend启动过程时,会在start Building... 卡住,然后提示一系列的报错。

复现过程很简单,可以在Windows系统上,部署运行一下frontend工程。

然后就会出现下面的问题问题

Image

Image

PS D:\fanWork\goWorkSpace\src\coze-studio\coze-studio-main\frontend\apps\coze-studio> rushx dev
Found configuration in D:\fanWork\goWorkSpace\src\coze-studio\coze-studio-main\rush.json

Rush Multi-Project Build Tool 5.147.1 - Node.js 22.11.0 (LTS)
> "rsbuild dev"

Rsbuild v1.1.13

fatal: not a git repository (or any of the parent directories): .git
➜ Network: http://192.168.30.15:8080/
➜ Network: http://192.168.145.1:8080/
➜ Network: http://192.168.222.1:8080/
➜ Local: http://localhost:8080/
➜ press h + enter to show shortcuts

[HPM] Proxy created: /api -> http://localhost:8888/
start Building...
Got 211 contents for tailwind
error Compile error:
Failed to compile, check the errors for troubleshooting.
File: \\?\D:\fanWork\goWorkSpace\src\coze-studio\coze-studio-main\common\temp\default\node_modules\.pnpm\@flowgram.ai+fixed-layout-editor@0.1.28_@babel+core@7.27.4_react-dom@18.2.0_react-is@19.1.0_r_k3bblxn5t5v3vgfkd5x7abuy44\node_modules\@flowgram.ai\fixed-layout-editor\index.css:1:1
× Module not found: Can't resolve './fanWork/goWorkSpace/src/coze-studio/coze-studio-main/common/temp/default/node_modules/.pnpm/@rsbuild+core@1.1.13/node_modules/@rsbuild/core/compiled/style-loader/runtime/injectStylesIntoStyleTag.js' in '\\?\D:\fanWork\goWorkSpace\src\coze-studio\coze-studio-main\common\temp\default\node_modules\.pnpm\@flowgram.ai+fixed-layout-editor@0.1.28_@babel+core@7.27.4_react-dom@18.2.0_react-is@19.1.0_r_k3bblxn5t5v3vgfkd5x7abuy44\node_modules\@flowgram.ai\fixed-layout-editor'
╭─[2:22]
1 │
2 │ import API from "!./fanWork/goWorkSpace/src/coze-studio/coze-studio-main/common/temp/default/node_modules/.pnpm/@rsbuild+core@1.1.13/node_modules/@rsbuild/core/compiled/style-loader/runtime/injectStylesIntoStyleTag.js";
· ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
3 │ import domAPI from "!./fanWork/goWorkSpace/src/coze-studio/coze-studio-main/common/temp/default/node_modules/.pnpm/@rsbuild+core@1.1.13/node_modules/@rsbuild/core/compiled/style-loader/runtime/styleDomAPI.js";
4 │ import insertFn from "!./fanWork/goWorkSpace/src/coze-studio/coze-studio-main/common/temp/default/node_modules/.pnpm/@rsbuild+core@1.1.13/node_modules/@rsbuild/core/compiled/style-loader/runtime/insertBySelector.js";
╰────

@ ../../packages/common/flowgram-adapter/fixed-layout-editor/src/css-load.ts
@ ../../packages/components/resource-tree/src/index.tsx
@ ../../packages/workflow/playground/src/components/workflow-header/components/reference-modal/utils.tsx
@ ../../packages/workflow/playground/src/components/workflow-header/components/index.ts
@ ../../packages/workflow/playground/src/index.tsx
@ ../../packages/project-ide/biz-workflow/src/index.tsx
@ ../../packages/project-ide/main/src/index.tsx
@ ./src/routes/async-components.tsx
@ ./src/routes/index.tsx
@ ./src/app.tsx
@ ./src/index.tsx

全部提示添加到了附件中

我的环境是:
Windows 10 专业版
node 22.11.0
npm 10.9.0
pnmp 8.15.8
rush 5.147

我感觉像是前端自动加载依赖的时候,没有正确加载上,我看其他的人也问了这个问题,他们说在Linux或者mac os上都是能正常运行的。提示的日志我了下,根据这个路径寻找,是可以找到common下面的依赖的js,但是前端工程识别不到,看着像是Windows 系统对文件路径的解析与 Linux/macOS 有差异,在 ​路径分隔符​ 和 ​绝对路径格式​ 上,具体什么地方配置的,我搜了会儿,也没找到,寻求大佬援助了

感谢大佬能看一下咋回事

[log.txt](https://github.com/user-attachments/files/21964382/log.txt)

Contributor guide

Open the contributing guide

Research direction

Reproduce the failure from frontend/apps/coze-studio with `rushx dev` on Windows, then inspect the generated CSS import and the path-related flow beginning at packages/common/flowgram-adapter/fixed-layout-editor/src/css-load.ts. Compare the resolved @rsbuild/core style-loader paths with the dependencies under common/temp/default/node_modules. Done means the frontend builds past the reported module-resolution error on Windows.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
build-system, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.