This repository is the Remix framework monorepo, implemented as a modular collection of 50+ independently versioned TypeScript packages under `packages/*`, all re-exported through a single `remix` meta-package. In production it provides a full-stack web framework built directly on Fetch/Streams standards: a typed fetch-first router with composable middleware, a custom JSX/Virtual DOM component runtime with SSR, hydration, frames, and CSS-in-JS, an asset server and compiler pipeline, authentication/session/security middleware, typed data validation and relational data-table packages with migrations, and a CLI for scaffolding, development, testing, and database operations. The repository is not a single deployable application; demos such as bookstore, social-auth, timeboxer, i18n, SSE, and the docs sites are first-party consumers that exercise the framework end-to-end.
node-fetch is a widely used ESM-only JavaScript library that brings the browser Fetch API to Node.js. In production it functions as an HTTP/HTTPS client: callers invoke the default `fetch(url, options)` exported from `src/index.js` and receive a `Response` backed by native Node.js Readable streams. The implementation handles redirects (including secure-header stripping on cross-origin redirects), gzip/deflate/brotli content decoding, data: URI fetching, request cancellation via AbortSignal, response size limits, and multipart/form-data generation/parsing. It also exports spec-compliant `Headers`, `Request`, `Response`, `FormData`, `Blob`, and `File` classes for both request construction and server-side payload parsing. Architecturally, the code is a modular library, not a service: `src/body.js` provides the shared Body mixin; `src/request.js` and `src/response.js` build on it; `src/headers.js` implements the Web IDL Headers interface; `src/index.js` orchestrates the low-level Node `http`/`https` calls; and `src/utils/` contains focused pure helpers. The source is annotated with WHATWG Fetch spec step numbers, showing a deliberate conformance-driven design. Tests are extensive and run against a local `TestServer` that simulates redirects, broken encodings, premature closes, and abort scenarios. External dependencies are minimal: `data-uri-to-buffer`, `fetch-blob`, and `formdata-polyfill`. The package declares Node `^12.20.0 || ^14.13.1 || >=16.0.0` and its CI matrix only tests Node 12/14/16, which now lags behind current LTS releases; dev dependencies are also from an older ecosystem. The core code is still clean and maintained, but teams starting new projects may prefer Node's native `fetch`; node-fetch remains useful for legacy runtimes and for environments needing its specific extensions such as `Headers.raw()` and custom agents.
HMPL.js is a lightweight JavaScript library for server-oriented HTML templating. It compiles templates with block helpers (e.g., `{{#request ...}}`) into functions that fetch HTML from a server, sanitize it via DOMPurify, and render it into the DOM. The library supports indicators, memoization, intervals, and status binding, and uses JSON5 for expressive attribute parsing. The core is a single TypeScript module (`src/main.ts`) that exports `compile`, `stringify`, `createWarning`, and `createError`. The repository also contains a comprehensive documentation site built with Astro + Starlight (including Vue interactive components) and a Jekyll blog. The codebase is well-tested with Mocha, Sinon, nock, and jsdom, and has CI/CD via GitHub Actions. It is primarily a frontend library but includes robust build and test infrastructure.
zlFetch is a lightweight JavaScript library that wraps the native Fetch API with quality-of-life improvements. It automatically parses response bodies based on `Content-Type` (JSON, text, form-urlencoded, NDJSON, Blob), provides promise-based error handling that rejects on 4xx/5xx status codes, supports request aborting, and includes shorthand methods for GET, POST, PUT, PATCH, DELETE. The library also offers streaming capabilities (SSE, NDJSON, chunked transfer), an EventSource wrapper for server-sent events, query string helpers, authorization header helpers, and a `createZlFetch` factory for pre-configured instances. The code is modular, well-typed with JSDoc, and thoroughly tested across browser and Node.js environments using vitest.
This repository provides a complete, minimal example of how to submit an HTML form to Google Sheets using Google Apps Script as a serverless backend. The core is a Google Apps Script (form-script.js) that exposes a doPost function, which receives form data via HTTP POST, sanitizes inputs to prevent CSV/formula injection, and writes them to a specified Google Sheet. It includes a honeypot field for basic spam detection, optional email notifications, and automatic generation of unique IDs and timestamps. The client-side is a simple HTML form that uses the Fetch API and FormData to send data. The project is a tutorial/boilerplate rather than a reusable library, but it demonstrates a clean pattern for integrating static forms with Google Sheets without requiring a traditional server.
SkillSet is a single-page browser application that transforms a JSONResume skills section into an interactive D3 force-directed graph. The user uploads a JSON file, the front-end parses the skills array (categories with keywords and proficiency levels), and D3 renders a node-link diagram where category nodes connect to keyword nodes, with edge thickness reflecting proficiency. The visualization supports drag, click to highlight nodes, and double-click to reset. The architecture is a classic static-site front-end: HTML loads three script tags (D3 library, core visualization logic in `viz.js`, and UI/business logic in `app.js`), with a modern-ish CSS layout using CSS custom properties and grid. A Webpack build step exists but the production deployment still uses the unbundled script approach. The code is functional and clean for a demo, but lacks modularity, tests, and error-handling sophistication. It is a straightforward, well-documented showcase of D3 force layout applied to a common resume format, suitable for portfolio demos but not for production reuse without significant refactoring.