You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously, 'vue-marcos' was used for the first time because some features of Vue, such as defineOptions, could not meet the requirements. But now, the features of Vue 3.4 have largely satisfied most scenarios in Element-Plus. So, is it possible now to separate 'vue-marcos' at a fundamental level?
Or upgrade vue-marcos and a few other build packages vite, @vitejs/plugin-vue and @vitejs/ plugin-Vue-jsx versions
After a careful examination, I noticed that many of the build packages in the project are outdated e.g. rollup, and the build process is overly complicated. I'm not sure if there is a plan for restructuring, but I feel that I could contribute to it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Previously, 'vue-marcos' was used for the first time because some features of Vue, such as defineOptions, could not meet the requirements. But now, the features of Vue 3.4 have largely satisfied most scenarios in Element-Plus. So, is it possible now to separate 'vue-marcos' at a fundamental level?
Or upgrade vue-marcos and a few other build packages vite, @vitejs/plugin-vue and @vitejs/ plugin-Vue-jsx versions
After a careful examination, I noticed that many of the build packages in the project are outdated e.g. rollup, and the build process is overly complicated. I'm not sure if there is a plan for restructuring, but I feel that I could contribute to it.
Beta Was this translation helpful? Give feedback.
All reactions