Replies: 1 comment
-
Yes, but it's not typically what you want. Historically
Just import the client-only wasm file instead of the viewer wasm file during bootstrapping as in the bundler guide: import SERVER_WASM from "@finos/perspective/dist/wasm/perspective-server.wasm";
// // Don't do this
// import CLIENT_WASM from "@finos/perspective-viewer/dist/wasm/perspective-viewer.wasm";
// Do this
import CLIENT_WASM from "@finos/perspective/dist/wasm/perspective-js.wasm";
await Promise.all([
perspective.init_server(fetch(SERVER_WASM)),
perspective_viewer.init_client(fetch(CLIENT_WASM)),
]);
Not only is
I can't imagine how but I also don't know what you mean by "modularizing" - if you just mean "use the engine separately" as above, it really depends on what your expectations are. As I said above,
Maybe re-phrase this in light of my answers above? Perspective engine and viewer are separate, if you have ideas to improve on this or that are specific to your use case, please make them discrete. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I’m currently working on a project where we only need the Perspective engine and do not use perspective-viewer. However, while trying to exclude perspective-viewer and build a minimal, unbundled version, I ran into issues.
When attempting this setup, I encountered the following error:
This suggests that some dependencies are still expected, even though I’m trying to use only the engine. In v2, I couldn’t completely remove perspective-viewer and ended up with an inline build, which I assume still includes the full package.
Discussion Points
Beta Was this translation helpful? Give feedback.
All reactions