cjwhand opened a new issue, #17284: URL: https://github.com/apache/dolphinscheduler/issues/17284
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues. ### What happened Uncaught (in promise) SyntaxError: Must be called at the top of a `setup` function at Object.createCompileError (core-base.esm-browser.js:240:19) at createI18nError (vue-i18n.cjs:83:21) at useI18n (vue-i18n.cjs:1886:15) at useTable (use-table.ts:22:17) at Proxy.render (state-card.tsx:66:28) at renderComponentRoot (runtime-core.esm-bundler.js:6560:16) at ReactiveEffect.componentUpdateFn [as fn] (runtime-core.esm-bundler.js:5351:46) at ReactiveEffect.run (reactivity.esm-bundler.js:237:19) at setupRenderEffect (runtime-core.esm-bundler.js:5486:5) at mountComponent (runtime-core.esm-bundler.js:5260:7) <!-- Failed to upload "image.png" --> ### What you expected to happen I downloaded the source code from the official website: 🔗 https://dolphinscheduler.apache.org/zh/en/download/3.1.9 File: apache-dolphinscheduler-3.1.9-src.tar.gz After extracting, I tried to start the UI (frontend only), and an error occurred even without starting the backend service. The issue is reproducible regardless of Node.js version — I've tested with Node.js 16, 18, 20, and 22, but the error still appears. It seems this is a frontend-related issue. I hope someone can help or confirm if others are experiencing the same problem. ### How to reproduce Start the UI (frontend only), and an error occurred even without starting the backend service. ### Anything else _No response_ ### Version 3.1.x ### Are you willing to submit PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
