liveBook · Manning

JavaScript

As explained in Vanilla Web

A programming language standardized as ECMAScript and widely used to implement behavior in web browsers.

JavaScript supplies behavior in browser applications: it coordinates data flow and state, and adds dynamic features to HTML and CSS. Vanilla JavaScript means using the core language and browser APIs without relying on a large library or framework. HTML still defines structure, and CSS still defines presentation. section 5.0 section 2.3

Keep the language distinct from the platform APIs it calls. Many browser capabilities require both JavaScript and a Web API, but most browser APIs are specified separately from the ECMAScript language. This distinction matters when checking whether a feature is available. section 3.8 section 5.1

For a browser-native implementation:

  • Use JavaScript to enhance semantic HTML and CSS rather than treating a framework as a prerequisite. section 5.0 section 1.6
  • Use ES Modules to organize code, and handle errors so an application remains robust without an external library. section 5.0
  • Choose dependencies according to requirements. Direct platform use can reduce layers, but a vanilla approach need not rule out small libraries or tools. section 2.3 section 1.6

ECMAScript is the standard under which JavaScript language features evolve. TC39 proposals pass through stages before entering an annual edition. Stage 4 means standardized, not immediately available in every browser: engines ship individual features on their own schedules. Target the browsers you support, not an edition label, and check compatibility through MDN, Baseline, or Can I Use—especially for newer proposals. Unlike a transpiled framework project, vanilla code is often shipped substantially as written unless you choose a build tool. section 5.1 section 5.0

Table 5.1 The TC39 process stages before becoming part of the ECMAScript standard
Stage Meaning

Stage 0

Strawman: an initial idea or proposal, not yet formally accepted, often experimental.

Stage 1

Under Consideration: the committee accepts it as worth exploring. The feature will be specified in detail, but it may undergo significant changes or be dropped.

Stage 2

Draft: the syntax and semantics are defined. Browser vendors may start implementing for testing purposes, but it is not yet final.

Stage 2.7

Approved: the syntax and semantics are approved.

Stage 3

Candidate: the feature is complete and is undergoing feedback from implementers and developers. Major browsers usually experiment here.

Stage 4

Complete: the feature is ready to be part of the ECMAScript standard. It will be included in the next yearly edition.

Consult the proposal-stage table to distinguish experimental features from completed ones; then verify browser support separately. section 5.1

How Vanilla Web covers it

How deep it goes
Defines Vanilla JavaScript and explains proposal stages, while previewing rather than working through modules, syntax, and error handling.
Examples
Uses a TC39 stage table and a comparison between transpiled framework code and directly shipped vanilla code.
What it assumes
Assumes HTML and CSS fundamentals while introducing modern JavaScript syntax, modules, and error handling.
What you can do after
Evaluate/understand it by checking browser support for proposed features rather than relying on ECMAScript edition labels.
How it connects
Connects JavaScript to semantic HTML, CSS, browser APIs, ES Modules, ECMAScript, and progressive web applications.

Also explained in

Compare how 18 books explain JavaScript →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vanilla Web. The section links point to the parts of the book it draws on.