GitHub - node-projects/esprima-next: fork of esprima, with full ES2022 supportYou signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Faster script loading with BinaryAST?
The performance of applications on the web platform is becoming increasingly bottle necked by the startup (load) time. Large amounts of JavaScript code are required to create rich web experiences that we’ve become used to. When we look at the total size of JavaScript requested on mobile devices from HTTPArchive, we see that an average page loads 350KB of JavaScript, while 10% of pages go over the
shapesecurity/shift-spec: Shift AST Specification
This document defines an interface for an abstract syntax tree that can be used to represent the structure of an ECMAScript program. The interface is intended to be able to represent any structurally valid ECMAScript program (according to the latest version of ECMA-262) while minimising the number of invalid programs that may be represented. This specification is defined using the Web IDL standard
impinball/es6-module-ast-proposal · GitHub
README.md Note: All source code in this repository is under the Unlicense. Proposal for SpiderMonkey AST representation for import and export statements The current AST format is both inconsistent and complicated. Esprima and Acorn have two different syntax trees for the same thing, and that currently heavily hinders inter-op between the two. Since the module syntax is stabilized, but I can tell t
ES6 module syntax update by caridy · Pull Request #287 · ariya/esprima · GitHub
Important Notice This is a non-backward compatible change in esprima:harmony branch since it removes some syntax from previous drafts that were specs recently and introduces the changes to align with the final draft. Issues https://code.google.com/p/esprima/issues/detail?id=597 Changes revision of ES6 import final syntax based on specs revision of ES6 export final syntax based on specs tests for i
Beyond Source Maps
There's been some recent talk on es-discuss about standardizing source maps in ECMAScript 7. Before that happens, we should take a moment to reflect on what source maps have done well, where they are lacking, and meditate on what a more perfect debug format for compilers targeting JavaScript might be. My response quickly outgrew an email reply, and so I am collecting my thoughts and posting them h
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
GitHub - alangpierce/sucrase: Super-fast alternative to Babel for when you can target modern JS runtimes
GitHub - estree/formal: ESTree machine-readable data (+generator)
GitHub - estree/estree: The ESTree Spec
Support ECMAScript 2015 syntax · Issue #555 · jsdoc/jsdoc
add support for ES6 · Issue #8 · shapesecurity/shift-parser-js
Add ECMAScript 6 features · Issue #10 · eslint/espree
Add ES6 Support · Issue #33 · estools/escope
GitHub - estools/esvalid: confirm that a SpiderMonkey format AST represents an ECMAScript program
GitHub - esnext/es6-arrow-function: Shorthand arrow functions compiled to ES5.
GitHub - millermedeiros/esformatter: ECMAScript code beautifier/formatter