What is this?
It is the source repository for the current draft of ECMA-262, the ECMAScript (JavaScript) Language Specification, maintained by TC39. The source is processed to generate the human-readable edition of the spec.
It is the source repository for the current draft of ECMA-262, the ECMAScript (JavaScript) Language Specification, maintained by TC39. The source is processed to generate the human-readable edition of the spec.Is this a JavaScript engine or a library I can use in my code?Neither — it is the specification document itself, not software. The draft is written in markup and processed into the readable HTML edition that developers and engine authors read.
Neither — it is the specification document itself, not software. The draft is written in markup and processed into the readable HTML edition that developers and engine authors read.How do I build the spec locally?Clone the repo and run npm install, then npm run build to build the spec; npm run watch keeps a continuous build going. Output lands in the out directory, and npm run clean deletes it.
Clone the repo and run npm install, then npm run build to build the spec; npm run watch keeps a continuous build going. Output lands in the out directory, and npm run clean deletes it.What do I need installed to work on it?Node.js with npm. The toolchain, including the ecmarkup processor that renders the spec, is set up with npm install — no other runtimes are involved.
Node.js with npm. The toolchain, including the ecmarkup processor that renders the spec, is set up with npm install — no other runtimes are involved.What is ecmarkup?The authoring toolchain this spec is written in. The build script runs ecmarkup on spec.html with --multipage to produce the multi-page HTML edition in the out directory.
The authoring toolchain this spec is written in. The build script runs ecmarkup on spec.html with --multipage to produce the multi-page HTML edition in the out directory.Is the draft automatically checked for errors?Yes. GitHub Actions workflows build the spec and type-check it with esmeta, and the default build runs with --lint-spec --strict, so spec-lint and formatting issues fail the build.
Yes. GitHub Actions workflows build the spec and type-check it with esmeta, and the default build runs with --lint-spec --strict, so spec-lint and formatting issues fail the build.Can I get the spec as a PDF?There is a dedicated script for that: npm run pdf builds a printable version with external assets and renders out/ECMA-262.pdf using Prince (prince-books).
There is a dedicated script for that: npm run pdf builds a printable version with external assets and renders out/ECMA-262.pdf using Prince (prince-books).What are similar projects?proposals, csharplang, swift-evolution, es6features, toml, fantasy-land, styleguide, guide
proposals, csharplang, swift-evolution, es6features, toml, fantasy-land, styleguide, guideWhich topics is it in?language-design, ecmascript, grammar, standards, specification, programming-language, computer-science, programming, ci, pdf, reference, documentation
language-design, ecmascript, grammar, standards, specification, programming-language, computer-science, programming, ci, pdf, reference, documentation