utopianet opened a new issue, #5492: URL: https://github.com/apache/linkis/issues/5492
### Search before asking - [x] I searched the [issues](https://github.com/apache/linkis/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? - [x] Yes I am willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
