You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 15, 2024. It is now read-only.
jsdom and nodecanvas causes a lot of compatibility problems with C++ compilers and latest NodeJS versions.
Let's use a custom build like:
After download the dev-build, we need to also remove extra require(...) calls so that webpack does not get confused with unused imports, and set fabric.isLikelyNode = false.
The text was updated successfully, but these errors were encountered:
* To cope with non-webpack-compatible build processes, imported
xterm.js and fabric.js into our own "vendor" directory.
- fabric.js is downloaded from the official customized builder
(http://fabricjs.com/build/) and slightly modified to remove
extra "reuqire()" calls that confuse webpack.
- xterm.js is built from our fork (https://github.com/lablup/xterm.js)
and the color scheme in xterm.css is modified to match our flavor.
- In our fork of xterm.js, we have patched non-IME character inputs
for macOS/iOS Safari.
I had to add "interaction" component to avoid errors due to undefined _getNonTransformedDimensions (which is actually defined but for some reason it's not accessible).
jsdom and nodecanvas causes a lot of compatibility problems with C++ compilers and latest NodeJS versions.
Let's use a custom build like:
After download the dev-build, we need to also remove extra
require(...)
calls so that webpack does not get confused with unused imports, and setfabric.isLikelyNode = false
.The text was updated successfully, but these errors were encountered: