JavaScript and TypeScript · origins, standards, runtimes and security
A consolidated history of JavaScript and TypeScript, from Smalltalk, Scheme, Self and Java through browser scripting, ECMAScript, Node.js, npm, modern runtimes and selected security reports. Gregorian display, UTC. Sources checked 3 November 2026; selected milestones extend through the 21 October 2026 Node security releases.
Follow the strands
Use Separate by tags for origins, smalltalk, scheme, self, java, javascript, typescript, ecmascript, standardization, browsers, engines, nodejs, npm, deno, bun, static typing, tooling, or security. Tags overlap; a selected set combines matching entries. Open the attached concept cards for differences between language, engine, host API, type checker, module system and package registry.
The early influence links distinguish Java’s syntax/marketing context, Scheme’s functions and Self’s prototypes. Smalltalk contributes to the earlier object-language tradition and the later implementation lineage; the timeline does not invent a direct Smalltalk-to-JavaScript class-system inheritance. Prototype delegation remains relevant after ES2015 classes. JavaScript is not a subset of Java.
Dates and standards
A date labels the specific event: announcement, beta, production release, proposal, standards approval/publication, support milestone, disclosure or response. Annual ECMAScript entries use the edition’s publication month, not an invented day of universal browser adoption. ECMA-262 is the core language; DOM, internationalization, host modules, runtime APIs and WebAssembly have separate histories. There is no published ECMA-262 fourth edition. TypeScript’s own releases and the type-annotation proposal are not automatically ECMAScript standards.
Year-only records use 1 January and month-only records use the first day solely for plotting. Midnight UTC is never an asserted release time. Dashed entries mark coarse dating. Narrative/research dates are distinguished from later retrospective source dates. The first ECMA-262 entry follows the archive’s June 1997 edition label, while noting the creators’ differing September completion/release chronology. Node 0.6’s November 5 announcement is distinguished from the November 4 changelog date.
The bands are editorial navigation guides, not exact lifetimes or support commitments. Undirected arcs show selected chronology or documented contextual links. Arrowheads are used only for specified influence/implementation paths; neither proximity nor an arc alone establishes a cause. The source event’s historyLinks records each connection’s kind and explanation.
Read the security entries by layer
Representative coverage, not every CVE or a current patch checklist. Entries separate engine memory-safety bugs, native runtime/dependency issues, application-level XSS/prototype pollution, and malicious package publishing. left-pad is an availability incident, not mislabeled as malware. Report dates, fixed release dates and known exploitation are different; exploitation is mentioned only within the vendor’s stated scope. Follow the linked advisories for their full platform, version and configuration conditions.
TypeScript catches classes of source-level errors but its types do not authenticate packages, validate external input, or prove an engine’s native memory safety. Node’s type stripping is distinct from type checking. A compiler implemented in Go still normally produces/serves JavaScript-targeted applications. Permission mechanisms and vm contexts are not universal hostile-code sandboxes. The cards explain these distinctions with project documentation.
Sources and scope
Primary sources dominate: the JavaScript creators’ historical paper; language authors’ papers and project records; Ecma/ISO/W3C specifications; Microsoft’s TypeScript announcements; browser-engine and runtime release notes; vendor security advisories; and maintainer incident reports. Garrett’s Ajax essay is identified as a preserved mirror of the original. The timeline is selective: it does not list every framework, browser build, TC39 proposal or package advisory, and it makes no permanent “latest version” claim.
The cover is a modern unofficial JavaScript logo, not a Netscape-era historical logo. Portraits illustrate the people; their capture dates are not the dates of the events they accompany. Commons licensing records were checked. Source files are linked directly, without synthetic depictions of incidents or borrowed exploit screenshots.
Duration correction: Ongoing subjects previously drawn through a present/research cutoff are represented at their original starts, with no end asserted. Existing moments at those coordinates are reused; their attached cards retain the former duration’s notes, sources, tags and media. Bounded historical and coverage intervals remain durations.
117 moments · 1972 CE – 2026-10-21 CE · by @athan · @athan
jQuery debuts
tooling
jquery
dom
interop
John Resig’s jQuery library offered concise document selection, manipulation and event handling across browser differences. It reduced repeated compatibility work for web developers while remaining ordinary library code layered over the browser’s language and document facilities. **This milestone:** John Resig introduces a library for concise DOM operations and cross-browser behavior. Libraries helped applications manage browser differences without changing JavaScript’s language specification. **Event type:** library release. **Date:** 2006-01-14. **Dating:** Day-level release, announcement, publication or response date; midnight does not assert a time of day. Gregorian display, UTC. Day records use midnight solely as a display anchor. A month-only event uses its first day and a year-only event uses January 1; neither asserts that occurrence day. Publication, approval, release, proposal and security-response dates are labeled separately. **Sources:** - [jQuery 4.0.0 | Official jQuery Blog](https://blog.jquery.com/2026/01/17/jquery-4-0-0/) **Source timing:** the 2026 project anniversary announcement explicitly recalls the January 14, 2006 introduction; it is not plotted at the retrospective article’s date. **Timeline anchor:** 14 January 2006 CE. Day-level release, announcement, publication or response date; midnight does not assert a time of day.
Date precision
Day-level release, announcement, publication or response date; midnight does not assert a time of day.
Coordinate convention
Gregorian display, UTC. Day records use midnight solely as a display anchor. A month-only event uses its first day and a year-only event uses January 1; neither asserts that occurrence day. Publication, approval, release, proposal and security-response dates are labeled separately.