circagraph01
Download
Offline browser HTML Desktop · Linux (.deb) Desktop · Linux (.AppImage) Desktop · Rocky / RHEL 10 (.rpm) Desktop · macOS Apple silicon (.dmg) Desktop · macOS Intel (.dmg) Desktop · Windows (.exe) Release notes & all downloads
Browser draft

Timeline controls

New here? The tour shows the main controls one at a time.

Modern unofficial yellow JavaScript JS logo, used to identify the subject rather than as a historical 1995 mark. Public domain via Wikimedia Commons.

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.

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·A local draft, ready to explore
TimelineAll moments
→

Moment details

Separate

Each separation moves the events with any of its tags into a track of its own, above the rest of the timeline. Nothing is changed or saved.

    Views

    A view is a saved set of separations (tags, disjoins and unions, or an event's relationships) for showing this timeline a particular way.

    Save a view

    Who can see it

    Share a view

    Who can see it

    The link opens the timeline in this view, for those who can see it.

    Shared with

    Add a disjoin or union

    Kind

    Shift or scale times

    Each time becomes (time − around) × scale + around + offset, exactly, as comparisons align timelines. A duration’s start or end that follows a moment moves with that moment.

    Apply to

    Search this timeline

      Durations in this view

        Choose a moment

          Pull requests

          Discussion

          Recommend timeline changes

          Your draft becomes a pull request. The upstream timeline stays unchanged until someone with write access merges it.

          Timeline plugins

          Plugin suites

          A suite adds several plugins at once. Plugins this timeline already has stay as they are.

          Create a suite

          Package this timeline's plugins to add them to other timelines at once. The suite carries each plugin's definition, custom plugins included.

          Plugins

          Plugin editor

          Define metadata fields and a restricted render script. No DOM, network, imports, loops or arbitrary calls. Later plugins override earlier effects. Installing takes effect immediately; publishing makes this version public in the server library.

          Plugin library

          Popularity counts public timelines with the plugin enabled.

          Compare timelines

          Select two to eight timelines visible to your account, or add a JSON file.

          Choose a shared time display

          These timelines use different printers or parsers. Choose the display for this comparison. Original times stay unchanged; use scale and offset to align different coordinate conventions.

          Show

          Hide parts of the timeline while you read it. Only this tab is changed, not the timeline.

          Timeline

          Charts

          Measures

          Measures are exact quantities that events carry, such as a cost or hours worked. Each event gives its own values, and every value is exact.

          Timeline time display

          These settings belong to this timeline and are included in saved files and server copies. Times stay exact.

          Numeric labels are rounded. SI prefixes work best with unit symbols such as s. A Julian year is exactly 365.25 days.

          Displayed value = (stored time − origin) / scale. For Gregorian display, the displayed unit is one second from 1970-01-01T00:00:00Z.

          Preview uses the current window span and viewport width. Custom helpers: hasView(), viewLeft(), viewRight(), viewSpan(), viewWidth(), unitsPerPixel(), labelResolution(), purpose(). Existing printers and parsers can ignore this context.

          New timeline from files

          A moment for each file, dated as you choose. Its source is the file itself: open it from the moment in the file's own app. Nothing is copied, and file paths are never saved to a server.

          Folders and files
            Which files
            Date each moment by
            Metadata

            Servers

            The official server is https://circagraph.org. You can connect to your own HTTPS servers too, and sign in to several at once: your timelines from each are listed together. Local .och files work without a connection.

            Your Circagraph account

            Private timelines, collaborators, and public sharing.

            Registration and account security settings are available on the website.

            Share this timeline.

            Collaborators

            Edits saved meanwhile

            Keep your versions to replace what was saved, or use the saved versions to drop your edits to these. Your other edits are saved either way.

            Delete moment?

            Choose date and time

            Uses this timeline’s time display. Leaving the text unchanged preserves the exact coordinate, even when the display rounds it.