How project packaging ignores vue CDN references. Because when this cdn cannot be accessed, the project cannot be accessed!

[uddsoft]

• I have searched the issues of this repository and believe that this is not a duplicate.

Version

1.7.7

Environment

vue@2.6.14

Reproduction link

https://add.waimaotools.com/user/login

Steps to reproduce

vue.config.js 文件内容：
js: [
'//cdn.jsdelivr.net/npm/vue@2.6.14/dist/vue.min.js',
'//cdn.jsdelivr.net/npm/vue-router@3.5.1/dist/vue-router.min.js',
'//cdn.jsdelivr.net/npm/vuex@3.1.1/dist/vuex.min.js',
'//cdn.jsdelivr.net/npm/axios@0.21.1/dist/axios.min.js'
]

What is expected?

当cdn地址不能访问，后台就不能使用了！

What is actually happening?

当这个地址不能访问的时候（cdn.jsdelivr.net/npm/vue@2.6.14/dist/vue.min.js），前端等待状态。

---

因为cdn依赖不一定每个用户都能访问，当用户不能访问的时候，前端会打不开。想把页面引用cdn依赖的方式，改为本地。

[uddsoft]

[github-actions]

Hello @uddsoft, we use GitHub issues to trace bugs or discuss plans of Ant Design Vue. So, please don't ask usage questions here. You can try to open a new discussion in antdv discussions, select Q&A to ask questions, also can ask questions on Stack Overflow or Segment Fault.

你好 @uddsoft，Ant Design Vue Issue 板块是用于 bug 反馈与需求讨论的地方。请勿询问如何使用的问题，你可以试着在 antdv discussions 新开一个 discussion，选择 Q&A 类别进行提问，也可以在 Stack Overflow 或者 Segment Fault 中提问。

[uddsoft]

我已经有好几个用户，因为cdn依赖引用无法访问。最后导致后台不能访问。您看看这算bug，还是使用讨论！

[uddsoft]

前端代码：
<!-- require cdn assets js --> <% for (var i in htmlWebpackPlugin.options.cdn && htmlWebpackPlugin.options.cdn.js) { %> <script type="text/javascript" src="<%= htmlWebpackPlugin.options.cdn.js[i] %>"></script> <% } %>
vue.config.js 代码：
const assetsCDN = { // webpack build externals externals: { vue: 'Vue', 'vue-router': 'VueRouter', vuex: 'Vuex', axios: 'axios' }, css: [], // https://unpkg.com/browse/vue@2.6.10/ js: [ '//cdn.jsdelivr.net/npm/vue@2.6.14/dist/vue.min.js', '//cdn.jsdelivr.net/npm/vue-router@3.5.1/dist/vue-router.min.js', '//cdn.jsdelivr.net/npm/vuex@3.1.1/dist/vuex.min.js', '//cdn.jsdelivr.net/npm/axios@0.21.1/dist/axios.min.js' ] }

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.