[Bug]: Got SyntaxError & ReferenceError when Importing waline.js v3 by CDN | 通过CDN导入waline.js v3时得到语法错误与引用错误 about waline HOT 7 CLOSED

https://unpkg.com/@waline/[email protected]/dist/waline.umd.js 用这个地址

https://unpkg.com/@waline/[email protected]/dist/waline.umd.js Use this address

from waline.

Thank you for your detailed explanation.
感谢您细心解答。

from waline.

不客气~
ps. Waline 仓库有 GitHub Action 工具，支持自动翻译中文内容补充到 issue 中，所以如果觉得麻烦，可以只发中文内容就行~

You're welcome~
ps. The Waline warehouse has a GitHub Action tool that supports automatic translation of Chinese content and adds it to the issue, so if you find it troublesome, you can just post the Chinese content~

from waline.

https://unpkg.com/@waline/[email protected]/dist/waline.umd.js 用这个地址

https://unpkg.com/@waline/[email protected]/dist/waline.umd.js Use this address

Thank you for your solution. Waline can load now and without errors, including the errors I mentioned above.
I suggest that this tip should be added to the document, at https://waline.js.org/en/cookbook/import/cdn.htmlso that ones in need get the solution easier. Should I make a pull request to add this?

感谢您的解答。现在Waline可以正常加载出来，不再出现我在上面提到的error或其他error。
我建议将这一条加入Waline文档的这个页面，好让需要的人更容易地获取到解决方案。请问我是否应该为文档提交一个pull request来添加这个内容？

from waline.

不用更新文档，本质是 @waline/hexo-next 没有使用 ES Module 的加载方式 <script type="module">，所以需要使用 UMD 的模块。文档本身是没有问题的。

There is no need to update the document. The essence is that @waline/hexo-next does not use the ES Module loading method <script type="module">, so it needs to use UMD modules. There is nothing wrong with the documentation itself.

from waline.

@waline/hexo-next 需要更新一下么？我不是很熟悉hexo那边的东西

@waline/hexo-next Do you need to update it? I'm not very familiar with hexo stuff.

from waline.

@waline/hexo-next 我思考了下，暂时不更新了。主要有几点考虑：

1. 现阶段是有方案使用 v3 的
2. 用户的配置是一个 url，代码层面可能不太好知晓它是否需要使用 es module 的模式加载。可能还是会有类似的 issue 出来。除非我们增加是否是 module 的配置，但感觉也没有太大的必要

@waline/hexo-next I thought about it and won’t update it for the time being. There are several main considerations:

1. At this stage, there are plans to use v3
2. The user's configuration is a URL, and it may not be easy to know at the code level whether it needs to be loaded using the es module mode. There may still be similar issues coming out. Unless we add the configuration of module, but it doesn’t feel necessary

from waline.