pixellint 0.31.12 → 0.33.0

package/README.md

@@ -1,7 +1,7 @@
 # pixellint
 
 Validator for pixels, postbacks, conversion API payloads, and tracking URLs,
-as a WASM-backed npm package. Same engine, same rule ids, and same evidence
+as a WASM-backed npm package for Node.js 18 or newer. Same engine, same rule ids, and same evidence
 levels as the [`pixellint` CLI](https://crates.io/crates/pixellint). Paste a
 URL or a CAPI JSON body at [pixellint.org](https://pixellint.org).
 
@@ -47,7 +47,7 @@ finding.targets[0];       // { component: "whole_url", start: 0, end: 46, ... }
 - URL conformance, transport, credentials, fragments, and ad-tech macro handling
 - IAB consent signals: TCF `gdpr` and `gdpr_consent`, the deprecated US Privacy
   string, and GPP `gpp` and `gpp_sid`
-- Vendor parameter contracts for 133 endpoint families, including Meta
+- 159 vendor rulepacks across 85 vendors, including Meta
   Conversions API, TikTok Events API, Reddit CAPI, and the browser pixels
 - Endpoint attribution for 120 vendor rows, so an unrecognized pixel still gets a name.
 
@@ -68,8 +68,23 @@ finding.targets[0];       // { component: "whole_url", start: 0, end: 46, ... }
 `vendor` for a caller's claimed vendor. `html`, `js`, and `gtm` throw: extract
 URLs first.
 
-Templates keep their macros: pass `{ state: "template" }` and unexpanded macros
-stop being findings.
+Use `{ kind: "request" }` with a serialized complete capture containing string
+`url`, string `method`, `headers` as an object or name/value list, and optional
+raw string `body`. It binds payload checks to the destination and adds method
+and header contracts. See [the HTTP capture schema](https://github.com/aleksUIX/pixellint/blob/main/docs/HTTP_REQUEST_SCHEMA.md)
+for representation limits and repeated fields.
+
+`vast` takes a tracking URL extracted from VAST and enables the IAB VAST
+macro-name checks. It does not accept a VAST XML document.
+
+Pass `{ state: "template" }` to allow unexpanded macros in a template.
+Macro syntax, position, and VAST macro-name checks still apply.
+
+## Browser integration
+
+This npm wrapper loads the Node-target WASM build. Its ESM entry uses
+`node:module`, so it cannot be imported directly in a browser. Build
+`pixellint-wasm` for a browser target and provide a browser loader.
 
 ## Links
 

package/index.d.ts

@@ -11,6 +11,14 @@ export type ArtifactKind =
 
 export type ExpansionState = "unknown" | "template" | "fired";
 
+/** Serialize this capture with JSON.stringify and validate with kind: request. */
+export interface HttpRequest {
+  url: string;
+  method: string;
+  headers: Record<string, string> | Array<{ name: string; value: string }>;
+  body?: string;
+}
+
 export type Severity = "error" | "warning" | "info";
 
 export type EvidenceLevel =

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pixellint",
-  "version": "0.31.12",
+  "version": "0.33.0",
   "description": "Validator for pixels, postbacks, conversion API payloads, and tracking URLs: Meta CAPI, Facebook pixel, GTM, and vendor rulepacks",
   "license": "Apache-2.0",
   "author": "Aleks <aleks@vastlint.org>",

package/wasm/pixellint.js

@@ -143,6 +143,10 @@ function __wbg_get_imports() {
             const ret = new Object();
             return ret;
         },
+        __wbg_now_89df1f68663e7e81: function() {
+            const ret = Date.now();
+            return ret;
+        },
         __wbg_set_6be42768c690e380: function(arg0, arg1, arg2) {
             arg0[arg1] = arg2;
         },