Package Exports
- @arcjet/analyze
- @arcjet/analyze/index.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@arcjet/analyze) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
@arcjet/analyze
Arcjet helps developers protect their apps in just a few lines of code. Implement rate limiting, bot protection, email verification & defend against common attacks.
This is the Arcjet local analysis engine.
Installation
npm install -S @arcjet/analyzeExample
import { generateFingerprint, isValidEmail } from "@arcjet/analyze";
const fingerprint = generateFingerprint("127.0.0.1");
console.log("fingerprint: ", fingerprint);
const valid = isValidEmail("hello@example.com");
console.log("is email valid?", valid);Implementation
This package provides analyze logic implemented as a WebAssembly module which will run local analysis on request details before calling the Arcjet API.
The arcjet.wasm.js file contains the binary inlined as
a base64 Data URL with the application/wasm MIME type.
This was chosen to save on storage space over inlining the file directly as a Uint8Array, which would take up ~3x the space of the Wasm file. See Better Binary Batter: Mixing Base64 and Uint8Array for more details.
It is then decoded into an ArrayBuffer to be used directly via WebAssembly's
compile() function in our entry point file.
This is all done to avoid trying to read or bundle the Wasm asset in various
ways based on the platform or bundler a user is targeting. One example being
that Next.js requires special asyncWebAssembly webpack config to load our
Wasm file if we don't do this.
In the future, we hope to do away with this workaround when all bundlers properly support consistent asset bundling techniques.
API
In progress.
License
Licensed under the Apache License, Version 2.0.