We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
我对比了build-plugin-rax-component0.x和build-plugin-component1.x的内容,发现在target为miniapp的情况下,build-plugin-component1.x里会将预设的模板拷贝进当前用户的工程目录
这里显得不太合理,既然在miniapp情况下交付给miniapp-compile-config来负责webpack的配置和工程构建,那么为啥要在调度miniapp-compile-config的build-plugin-component层面中加入模板复制呢?导致与miniapp相关的构建不是单一职责了
另外模板中的内容也是写死的(src/template/miniapp/ali-miniapp),如果不同业务方需要定制不同内容的小程序模板,目前只能通过在build-scripts层通过加入plugin改写webpackChain配置来实现(有没有合适的改写时机都还不知道),这样显得挺复杂。。。
于是对于miniapp构建来讲,build-plugin-rax-component0.x的使用体验就明显比build-plugin-component1.x好不少。
The text was updated successfully, but these errors were encountered:
No branches or pull requests
我对比了build-plugin-rax-component0.x和build-plugin-component1.x的内容,发现在target为miniapp的情况下,build-plugin-component1.x里会将预设的模板拷贝进当前用户的工程目录
这里显得不太合理,既然在miniapp情况下交付给miniapp-compile-config来负责webpack的配置和工程构建,那么为啥要在调度miniapp-compile-config的build-plugin-component层面中加入模板复制呢?导致与miniapp相关的构建不是单一职责了
另外模板中的内容也是写死的(src/template/miniapp/ali-miniapp),如果不同业务方需要定制不同内容的小程序模板,目前只能通过在build-scripts层通过加入plugin改写webpackChain配置来实现(有没有合适的改写时机都还不知道),这样显得挺复杂。。。
于是对于miniapp构建来讲,build-plugin-rax-component0.x的使用体验就明显比build-plugin-component1.x好不少。
The text was updated successfully, but these errors were encountered: