Andrew Stein

May be a bit more complex than that, as the general rules for module resolution are somewhat arbitrary (e.g. jsdelivr also respects a `jsdelivr` field when present, and newer versions...

If I just change the output location to `dist`, this will work I assume?

Thanks for the report @shinny-yangyang! We did not dist Windows wheels for Perspective's `1.0.7` perspective release due to a regression, and you do not have the needed dependencies to build...

Looks like [`3.10` has some CI issues](https://dev.azure.com/finosfoundation/perspective/_build/results?buildId=3842&view=results) so this won't make `1.0.8`, we'll track this issue here.

Some additional context - * It's certainly true that the Rust/WASM output as configured in this patch does not output svelte assets. The time-to-idle for a page though is not...

I've reorganized this a bit, though it will not currently build until azure is updated to include `rustup` and `wasm-pack` tools it should build fine locally: * Moved the project...

Thanks for the question @rmdort ! `TOTAL` is an aggregation of the values by row. There is no way to currently tell Perspective to only aggregate rows to the `TOTAL`...

Thanks for the report! This just looks like a bug - the plugin is merely trying to resolve the path though, it does not actually use `@finos/perspective-viewer`, so you should...

I don't know anything about Vite, but Perspective should build fine in Vite without a plugin [as per docs](https://perspective.finos.org/docs/md/js.html#webpack-plugin-optional) - does it not currently? The `perspective-webpack-plugin` just optimizes the build...

Thanks for the report @iscanegemen ! This is a known issue, stemming from the fact that several disparate notions of equality in perspective use the same operator overloads that ExprTK...