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.
Start with JavaScript: The First 20 Years, Self’s project history, Ecma’s edition archive, TC39’s process, TypeScript’s original public debut, and Node’s release and advisory archive. Each entry carries its own references and dating note.
Media credits
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.
- Ramaksoud2000 via Chris Williams · JavaScript-logo.png · Public domain; rights.
- Microsoft, etc · TypeScript Logo.png · Public domain; rights.
- Darcy Padilla · Brendan Eich Mozilla Foundation official photo.jpg · CC BY-SA 3.0; rights.
- DBegley · Anders Hejlsberg.jpg · CC BY 2.0; rights.
- David Calhoun · Ryan Dahl.jpg · CC BY 2.0; rights.
- Marcin Wichary from San Francisco, U.S.A. · Alan Kay (3097597186).jpg.jpg) · CC BY 2.0; rights.
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
Moments
- Smalltalk-72 makes an interactive object world
- Scheme introduces its compact Lisp model
- Ungar and Smith design Self around prototypes
- Self: The Power of Simplicity describes the design
- Berners-Lee proposes the Web at CERN
- The Green Project begins the path from Oak to Java
- NCSA releases Mosaic 1.0
- Eich builds the Mocha prototype at Netscape
- Sun announces Java and Netscape’s licensing plan
- Navigator 2 beta exposes LiveScript
- Netscape and Sun announce the JavaScript name
- LiveWire offers server-side JavaScript before Node
- Navigator 2 ships JavaScript 1.0
- Internet Explorer 3 ships Microsoft’s JScript
- The ECMAScript standardization effort starts at Ecma
- ECMA-262 edition 1 is published
- Netscape opens its browser source; Mozilla begins
- ECMA-262 edition 2 is published
- DOM Level 1 becomes a W3C Recommendation
- ISO/IEC 16262:1998 publishes ECMAScript internationally
- ECMA-262 edition 3 is published
- Microsoft patches IIS cross-site scripting vulnerabilities
- Apple introduces the Safari public beta
- Firefox 1.0 is released
- Garrett names the Ajax application pattern
- jQuery debuts
- RFC 4627 documents JSON
- JavaScriptCore adopts the SquirrelFish interpreter
- Harmony redirects work away from the ES4 design
- Mozilla announces TraceMonkey
- Chrome launches with the open-source V8 engine
- Ryan Dahl introduces Node.js
- ServerJS calls for a usable server-side module ecosystem
- ECMA-262 edition 5 is published
- npm 1.0 is released
- ECMA-262 edition 5.1 is published
- Node 0.6 expands cross-platform support
- Microsoft publicly unveils TypeScript 0.8
- CSP 1.0 reaches W3C Candidate Recommendation
- ECMA-402 standardizes internationalization APIs
- Node 0.10 brings the Streams2 era
- Chromium announces the Blink rendering-engine fork
- React is open-sourced
- TypeScript 0.9 introduces generics
- TypeScript 1.0 is released
- Facebook introduces Flow for JavaScript type checking
- io.js forks Node amid governance and release concerns
- Annual ECMAScript editions
- TypeScript 1.4 adds union types and type guards
- 6to5 becomes Babel