crossbind
GitHub

SpatiaLite

v5.1.0Database

SpatiaLite 5.1.0, spatial SQL extension for SQLite, packaged by crossbind as @crossbind/port-spatialite and one package per target. Only a variant that is actually on npm beta is listed as published.

npm install @crossbind/port-spatialite@beta

Packages

TargetPackagenpm `beta`
Meta package@crossbind/port-spatialite2.0.0-beta.56
Web and Node.js@crossbind/port-spatialite-wasm2.0.0-beta.56
WASI library@crossbind/port-spatialite-wasi2.0.0-beta.56
Android@crossbind/port-spatialite-android2.0.0-beta.56
iOS@crossbind/port-spatialite-ios2.0.0-beta.56

Install

Install the variant for the platform you build, declare it as a dependency in crossbind.config.js and import the header from JavaScript. Nothing is compiled on your machine. A project that builds for several platforms lists one variant per platform: @crossbind/port-spatialite-wasi, @crossbind/port-spatialite-android, @crossbind/port-spatialite-ios are published too.

shell
npm install @crossbind/port-spatialite-wasm@beta
crossbind.config.js
import spatialiteWasm from '@crossbind/port-spatialite-wasm/crossbind.config.js';
 
export default {
dependencies: [spatialiteWasm],
paths: { config: import.meta.url },
};

Header import paths are relative to the package's dist/prebuilt/<target>/include, so @crossbind/port-spatialite/<header>.h is upstream's own header. The full flow, including what the meta package is for, is in the Libraries guide.

Licence

  • npm license field of @crossbind/port-spatialite: MPL-1.1 OR GPL-2.0-or-later OR LGPL-2.1-or-later.
  • The licence files that ship with the package, and the port recipe, are in the port directory.

Facts on this page come from the port manifests in the repository and from what npm served on beta when the site was built. See the Libraries guide for the full consumer flow.

MORE LIBRARIES
cURLExpatGDALGEOSGeoTIFFiconvLERClibjpeg-turbolibTIFFOpenSSLPROJSQLiteWebPzlibZstandard
Type to search every guide page and section.
↑↓ navigate↵ openesc close