songjianet opened a new issue #7332: URL: https://github.com/apache/dolphinscheduler/issues/7332
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement. ### Description refactor reason - Use the updated technology stack to solve the problem of not supporting the `m1` series chips directly from the root cause, and at the same time can improve the startup speed and build speed of the project. - Solve the problem that some tools and dependencies used in existing projects are about to lose their maintenance. - Standardize code writing to enhance control over code style and specifications. - Solve the problem of style pollution caused by the styles in all `sfc` not using `scoped` in the project. - `jquery` is no longer used in the project. - Solve the problem of deep nesting of the directory hierarchy and irregular file storage in the project. - Solve the problem of extensive use of absolute positioning in the project. - Add front-end unit tests, use `jest` + `vtu` to ensure the stability of front-end components. Whether to use other methods to support `m1` Try to upgrade the existing project by using `node16`, then you need to upgrade `node-sass7`, the new version of `node-sass7` also needs to depend on `node-gyp8`, correspondingly, you need to upgrade `sass-loader12`, and then `webpack4` does not To know these, you need to upgrade `webpack5`, and then the old version of `babel` is not supported, and then upgrade `babel`. After upgrading `babel`, it is found that the existing `element` and `vue` both use the old version of `babel`. ### Use case use technology - node16 - vue3 - vue-router4 - vueuse - axios - pinia - vite - scss - naiveui - pnpm - data-fns - ts+tsx - jest + vtu ### Related issues _No response_ ### Are you willing to submit a 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]
