Results of 1 - 5 of about 5 for mvp (0.001 sec.)
- Instantiate 12446
- Overview DuckDB-Wasm can be instantiated in several ways, depending on how your application bundles and serves its assets. Each approach resolves the mainModule (the WebAssembly file) and the mainWorker (the worker script) for the browser's
.... Bundle Selection DuckDB-Wasm ships several WebAssembly modules compiled for different browser feature sets, because post-MVP WebAssembly features reach browsers at different speeds and each one can bring a flat performance improvement. The selectB...undle function runs dynamic browser checks and picks the fastest bundle the current browser supports: mvp — the WebAssembly 1.0 (MVP) baseline, supported everywhere eh — adds Wasm-level exception handling, which improves perform...declared manually because their final locations are known only after the build, and selectBundle then chooses between the mvp and eh variants at runtime. import * as duckdb from '@duckdb/duckdb-wasm'; import duckdb_wasm from '@duckdb/duckdb-wasm/di... - https://man.mtool.work/duckdb/2.0/clients/wasm/instantiation.html
- Deploy 10001
- Overview Deploying DuckDB-Wasm means serving its components so that the browser can fetch and instantiate them. This page describes each component a deployment needs to serve, how the worker and WebAssembly variants relate, how extensions a
...er example shows a minimal setup. JS Worker Component This is distributed as a JavaScript file in three different flavors, mvp , eh and coi , and needs to be served as-is. The main library component needs to be informed of the actual location. The t...hree variants target three different WebAssembly feature sets: mvp targets the WebAssembly 1.0 (MVP) spec eh targets WebAssembly with Wasm-level exception handling added, which improves per...wser. Like the JS Worker component, it comes in the same three flavors, each paired with the JS worker of the same flavor: mvp — for example duckdb-mvp.wasm , loaded by the mvp JS worker eh — for example duckdb-eh.wasm , loaded by the eh JS worker c... - https://man.mtool.work/duckdb/2.0/clients/wasm/deploying_duckdb_wasm.html
- Troubleshoot 7831
- Overview This page collects common issues encountered when using DuckDB-Wasm, together with their workarounds. If you run into a problem that is not covered here, search the duckdb-wasm issue tracker on GitHub. Network Error When Querying R
...ith the Cross-Origin-Embedder-Policy and Cross-Origin-Opener-Policy headers, DuckDB-Wasm falls back to the single-threaded mvp or eh bundle. See Cross-Origin Isolation for the required headers, and Threading for how to select and configure the coi b... - https://man.mtool.work/duckdb/2.0/clients/wasm/troubleshoot.html
- Building DuckDB from Source 7831
- When Should You Build DuckDB? DuckDB binaries are available for stable and preview builds on the installation page . In most cases, it's recommended to use these binaries. When you are running on an experimental platform (e.g., Raspberry Pi
...t Effort Support Platform name Description freebsd_amd64 FreeBSD x86_64 (AMD64) freebsd_arm64 FreeBSD AArch64 (ARM64) wasm_mvp WebAssembly Minimum Viable Product windows_amd64_mingw Windows 10+ x86_64 (AMD64) with MinGW windows_arm64_mingw Windows 1... - https://man.mtool.work/duckdb/2.0/dev/building/overview.html
- Extension Distribution 7776
- Platforms Extension binaries are distributed for several platforms (see below). For platforms where packages for certain extensions are not available, users can build them from source and install the resulting binaries manually . Most offic
...ns are distributed for the following platforms: linux_amd64_musl and linux_arm64_musl windows_amd64_mingw wasm_eh and wasm_mvp (see DuckDB-Wasm's extensions ) For platforms outside the ones listed above, we do not officially distribute extensions (e... - https://man.mtool.work/duckdb/2.0/extensions/extension_distribution.html
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work