-
When integrating the xterm in the electron+vue project on the windows platform. Uncaught TypeError: e.replaceChildren is not a functionWork Environment
Refer to xterm in projectconst term = new Terminal({ const fitAddon = new FitAddon(); Can anyone help to look this issue and point out where the mistake is? Thanks for your kindly help. |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments
-
What browser/version are you on? |
Beta Was this translation helpful? Give feedback.
-
Instead of using a browser, this library is used in the electron desktop client. eg: |
Beta Was this translation helpful? Give feedback.
-
What version of Electron are you on? The version of Electron uses a particular version of Chromium underneath which is very likely a version earlier than the last 2 versions. |
Beta Was this translation helpful? Give feedback.
-
@hongdyu Can you step debug this? What is Why I am asking - some frameworks do nasty rewrites of certain event handlers to fit their own DOM handling idea, so its not really safe to assume that |
Beta Was this translation helpful? Give feedback.
-
Hi Tyriar & jerch, btw, it also use the local-echo library to display message and support most of bash-like input primitives. |
Beta Was this translation helpful? Give feedback.
-
Well from there you have several options - either upgrade electron (which I'd recommend, since this is also about security patches). If thats not viable and you need a hotfix, maybe check babel for a polyfill or write your own (like this one). Last but not least, you can also revert the change (see #4217) and maintain your own copy of xterm.js, but that more involved to keep in sync in the long run. |
Beta Was this translation helpful? Give feedback.
Well from there you have several options - either upgrade electron (which I'd recommend, since this is also about security patches). If thats not viable and you need a hotfix, maybe check babel for a polyfill or write your own (like this one).
Last but not least, you can also revert the change (see #4217) and maintain your own copy of xterm.js, but that more involved to keep in sync in the long run.