测试库, XSS filter
RTIF HTML serialization plugin
Headless SDK for DA Structured Content: schema-driven JSON document editing, validation, and HTML serialization.
🌱 Lightweight offline DOM
Support for proto3 JSON serialiazation/deserialization for protobuf.js
Block serialization specification parser for WordPress posts.
Serialization for Keyv
JavaScript implementation of the BSER Binary Serialization
(De)serialization functions for the Cardano blockchain along with related utility functions
Compare, format, diff and serialize any JavaScript value
Remark plugin to support comments
Expo module implementation of a parser based on https://httpwg.org/specs/rfc8941.html
(De)serialization functions for the Cardano blockchain along with related utility functions
mcl ; A portable and fast pairing-based cryptography library for Node.js by WebAssembly
Implementation of Kiota Serialization interfaces for text
High-performance JSON serialization library
Implementation of Kiota Serialization interfaces for URI from encoded
Simple cross Node.js inteface for using brotli compression
Implementation of Kiota Serialization interfaces for multipart form data
Implementation of Kiota Serialization interfaces for JSON
A JSON polyfill for older JavaScript platforms.
This package contains HTML helpers and functionality for Lexical.
JSON canonicalize function
Ultra-fast and conformant CBOR (RFC 8949) implementation with support for numerous tag extensions including records and structured cloning
Serialize HTML tables into JSON in Ruby
A utility for building progressively enhanced Facebook dialogs
Canon provides canonicalization and pretty-printing for various serialization formats (XML, HTML, JSON, YAML), producing standardized forms suitable for comparison, testing, digital signatures, and human-readable output.
A microformats 2 h-entry parser. Fully Deprecated. Please see: https://rubygems.org/gems/microformats2
A hATOM feed parser
Scheme Parser parse an XML/HTML document to hashly-structured format, prepared to import to a DB, or just serialize it and save it as is
DRY your controllers and make your API more predictable by defining responders for different formats. E.g. Posting an invalid resource in HTML should render a form with errors, while in JSON you expect serialized errors.
**Non Functional / Still in Planning Stage** Here's the high-level (brain dump): * Site content is organized in collections * Collections are serialized * Each have support for next, previous, first, last, etc * The content files are HTML * Templates are object based (each content type can be rendered with their own templates) * Templates are HTML with interspersed Liquid markup * All meta data is described using HTML meta tags * You custom meta data tags in a content objects * You can specify 'prototype' content objects in a collection with a _proto folder in the collection
Extract structured information from text with source grounding, deterministic serialization, and HTML visualization.
Contentful API wrapper library exposing an ActiveRecord-like interface
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.