OpenCascade wasm/js library size

[stewartoallen]

The size of the WASM and JS to support this package is considerably smaller that the two files in the dist directory of the npm package. How did you produce the smaller files? By omitting some of the OCC apis?

An old hat at JS, but new to OCC and WASM, so please bear with me.

Thanks!

[Irev-Dev]

The module listed in package.json is a little misleading. It a different fork of opencascade.js, maybe there's more to it, but I think that's probably the explanation @stewartoallen.
https://github.com/zalo/opencascade.js

[stewartoallen]

I see now. Thanks. It uses a modifiedopencascade.idl to limit the APIs exposed. And that makes the size and load time manageable. The parent project exposes everything which is totally unworkable for a web app.

[Irev-Dev]

There's a bunch of relevant context in this PR too @stewartoallen
#12

[stewartoallen]

thanks for that pointer. the increased wasm size is definitely a problem and not really because of network transport. it takes about 40 seconds to instantiate the larger wasm after the bytes are loaded. the version being used in CascadeStudio takes about 7 seconds.