A short answer is no. Only user uploaded fonts are available now.

@eric Thank you. In case you plan to extend the official api in any way, I suggest that you also expose libraries used, like opentype.js. In my case I can include opentype.js together with the extension, so it's not a problem - but wasteful. May I ask a related question? What would be the best way to use additional libraries within an extension? Since all scripts of an extension get executed within their own anonymous function context, I have to attach the library to a global element, so I can use it from any other script of the extension. I think that maybe `easyeda.extension.instances.myextensionid.opentype = opentype` might be a good way to expose it, because it is my unique scope and it will also get deleted when my extension is unloaded, correct? 🤔

Since `opentype` is in global namespace, you can use it directly.

@eric ooops, I missed that 🙈 I'm also using paper.js in the extension and I was looking for the best way to load it, so I just assumed I had to do the same for opentype.js. I'm glat that I don't have to. But since I also have to load paper.js (which exposes `paper`) the same question applys. I don't want to load `paper` globally because, in theory, EasyEDA or another extension could also do that and may reuire a different version or etc. I'd like to stay in my own namespace if possible. I think that's what extions should do...

I understand your needs. A module system is required but easyeda has not provided. EasyEDA should improve it so that you can import scripts just like `require.js` or es module.