Browser-side HTML serializer for converting live DOM trees into structured JSON with layout, styles, fonts, transforms, and assets.
Serialize JavaScript to a superset of JSON that includes regular expressions and functions.
Parses, serializes, and manipulates MIME types, according to the WHATWG MIME Sniffing Standard
hast utility to serialize to HTML
Transform OpenTelemetry SDK data into OTLP
serialize html forms
Serialize/deserialize an error into a plain object
Serialization for Keyv
An addon for [xterm.js](https://github.com/xtermjs/xterm.js) that enables xterm.js to serialize a terminal framebuffer into string or html. This addon requires xterm.js v4+.
A per-spec XML serializer implementation
ASN.1 schema for elliptic-curve private keys and related identifiers defined in RFC 5915, RFC 5480, and RFC 3279.
TypeScript definitions for serialize-javascript
Stringify your JSON at max speed
serialize objects to javascript
A structuredClone polyfill
Serializes any DOM node into a String
very fast object redaction
ASN.1 schema for PKCS #8 private key information structures defined in RFC 5208.
Simple object hashing, serialization and comparison utils.
ASN.1 schema for Cryptographic Message Syntax (CMS) defined in RFC 5652.
> Serialize/deserialize an error into a plain object in commonjs
A library for simplifying encoding and decoding URL query parameters.
ASN.1 schema for PKCS #10 certificate signing requests defined in RFC 2986.
ASN.1 schema for RSA keys and algorithms defined in RFC 8017.
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.