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

[Bug] linkis-web-next build fails: router imports a non-existent file src/pages/ECMManagement/engine.vue

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

还没有人认领这个 Issue。

评估

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

调研方向

阅读 linkis-web-next/src/router/index.ts,并检查 linkis-web-next/src/pages/ECMManagement/;issue 称其中包含 index.vue 和 modal.vue,但没有 engine.vue。在 linkis-web-next 中运行 npx vite build,以复现缺失的导入。issue 建议添加缺失的页面以使路由正常工作,或者在没有计划支持该页面时删除路由;选定的更改解决构建失败后,即视为完成。

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

描述

bug dependencies
Search before asking
  • I searched the issues and found no similar issues.
Linkis Component

linkis-web

Steps to reproduce

cd linkis-web-next
npm install
npx vite build

Expected behavior

The production build of linkis-web-next fails out of the box because the router references a Vue page that does not exist anywhere in the repository.

linkis-web-next/src/router/index.ts declares the route /console/ECMManagement/engines/:instance with a lazy import of @/pages/ECMManagement/engine.vue, but the file linkis-web-next/src/pages/ECMManagement/engine.vue was never committed. The directory only contains index.vue and modal.vue.

The defect exists both in the release-1.8.0 tag and in the current master branch.

Your environment

Linkis version: 1.8.0 (tag release-1.8.0, commit e2909eaf); also reproduced on master
OS: Windows 10 22H2 (platform-independent issue)
Node.js: 18.20.4, Vite: 6.2.4

Anything else

vite v6.2.4 building for production...
transforming...
✓ 192 modules transformed.
✗ Build failed in 3.08s
error during build:
[vite:load-fallback] Could not load D:...\linkis-web-next\src/pages/ECMManagement/engine.vue
(imported by src/router/index.ts):
ENOENT: no such file or directory, open '...\linkis-web-next\src\pages\ECMManagement\engine.vue'

Root cause
linkis-web-next/src/router/index.ts (around line 116):

{
name: 'Engines',
path: '/console/ECMManagement/engines/:instance',
component: () => import('@/pages/ECMManagement/engine.vue'),
meta: {
title: 'ECM Engines',
publicPage: true,
},
},

linkis-web-next/src/pages/ECMManagement/ on master / release-1.8.0 contains only:

index.vue
modal.vue

Expected behavior
npx vite build (and npm run build) should complete successfully in a clean checkout.

Suggested fix (two options)
Add the missing engine.vue page (recommended — keeps the /console/ECMManagement/engines/:instance route functional). A minimal placeholder page is enough to restore the build and can be polished later. PR will follow.
Alternatively, remove the dead route from the router if the page is not planned.
I will submit a PR implementing option 1 shortly.

Are you willing to submit a PR?
  • Yes I am willing to submit a PR!
主要语言
Java
星标
3.4k
派生
1.2k
PR 合并指标
30 天内没有已合并 PR

环境准备

从这里开始

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

apache/linkis 的其他 Issue

查看 apache/linkis 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

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