Object rest and spread properties · V8
Show navigation Before discussing object rest and spread properties, let’s take a trip down memory lane and remind ourselves of a very similar feature. ES2015 array rest and spread elements #Good ol’ ECMAScript 2015 introduced rest elements for array destructuring assignment and spread elements for array literals. // Rest elements for array destructuring assignment: const primes = [2, 3, 5, 7, 11]
JSC 💕 ES6
Jun 5, 2017 by Saam Barati, Yusuke Suzuki & Filip Pizlo @saambarati Update: The previous version of this post showed performance data from ARES-6 version 1.0. Version 1.0 had a bug where the score for the Worst 4 Iterations was actually using the first 4 iterations. We have fixed the bug and updated the benchmark to version 1.0.1. The performance results shown in this post now use ARES-6 version 1
Why Object Literals in JavaScript Are Cool
Before ECMAScript 2015 object literals (also named object initializers) in JavaScript were quite elementary. It was possible to define 2 types of properties: Pairs of property names and related values { name1: value1 } Getters { get name(){..} } and setters { set name(val){..} } for computed property values Sadly, the object literal possibilities match into a single example:
HTMLのpattern属性とJavaScript正規表現のunicodeオプション - Hatena Developer Blog
Refactoring to an Adaptive Model
Most of our software logic is written in our programming languages, these give us the best environment to write and evolve such logic. But there are circumstances when it's useful to move that logic into a data structure that our imperative code can interpret - what I refer to as an adaptive model. Here I'll show some product selection logic in JavaScript and show how it can be refactored to a sim
(Babel 5における)ES6のモジュールを解説してみた - uehaj's blog
Introduction · ECMAScriptとは何か？
Introduction ECMAScriptとは何か？ECMAScriptの嘘は嘘と見抜けるように results matching "" No results matching ""
es6-coding-style/es6-coding-style-en.md at master · gf-web/es6-coding-style · GitHub
ECMAScript6 Style Guide - Frontend Team of GF Securities This style guide is based on standard specifications of JavaScript，only agreed for the ES6 related content Such as variable naming convention, whether to add a semicolon or not, please refer to JavaScript specification Note that the current code compiling tools ( such as Babel, Traceur) is not perfect , some features should be used with caut
ES6 でこのように書いている - Qiita
最初は引数の順番を気にしなくて良いとか、あとから雑な気持ちで引数を増やせて便利だなくらいに思っていたのだけど、最近はイベント発行側が受け取り側の変数名を束縛できるのでコードに一貫性を持たせられるというのが実はけっこう良いのではと思っている。 Symbol 2015/07/28 13:45 記述修正 外部からアクセスしにくい、もしくは重複しない変数を作るのに使っている。 import { EventEmitter } from "events"; export const EVENTS = typeof Symbol !== "undefined" ? Symbol("EVENTS") : "@mohayonao/${package-name}:EVENTS"; export default class SummerVacation extends EventEmitter { constr
A Formal Commitment to New Language Features
A Formal Commitment to New Language Features The JSHint team Jul 7th, 2015 In recent months, JSHint has been receiving requests to support proposed JavaScript language features like async/await, method decorators, and class property declarations [1]. The JSHint team has turned down each request, even after the release of ES2015. This has not been easy; as open source project maintainers, nothing g
You Might Not Need Underscore
You Might Not Need Underscore During past years utility libraries like Underscore and lodash have found their way into the toolchain of many JavaScript programmers. While those utility libraries might make the code easier for you to write, they don’t necessarily make the code simpler or easier to understand. People reading and maintaining the code are obliged to, in addition to knowing the languag
Metaprogramming in ES6: Symbols and why they're awesome
You’ve heard of ES6 right? It’s the new version of JavaScript that is awesome in so many ways. I frequently wax lyrical about all of the amazing new features I keep discovering with ES6, much to the chagrin of my colleagues (consuming someone’s lunch break talking about ES6 Modules seems to be not to everyone’s liking). A set of great new features for ES6 comes in the form of a slew of new metapro
ECMAScript 2015 Language Specification – ECMA-262 6th Edition
Standard ECMA-262 6th Edition / June 2015 ECMAScript® 2015 Language Specification This is the HTML rendering of ECMA-262 6th Edition, The ECMAScript 2015 Language Specification. The PDF rendering of this document is located at https://ecma-international.org/wp-content/uploads/ECMA-262_6th_edition_june_2015.pdf. The PDF version is the definitive specification. Any discrepancies between this HTML ve
Exploring ES6
What you need to know about this book Audience: JavaScript programmers Why should I read this book? How to read this book Sources of this book Glossary Conventions Demo code on GitHub Sidebars Footnotes Foreword Preface Acknowledgements About the author I Background 1. About ECMAScript 6 (ES6) 1.1 TC39 (Ecma Technical Committee 39) 1.2 How ECMAScript 6 was designed 1.3 JavaScript versus ECMAScript
Rails + React + ES6 のためのアセット環境構築 - 破いて捨てたノート
結論 Sprocketsの動作を維持しつつ、npmやgulpなどのモダンなパワーも取り入れた、いいとこどりな環境を構築してみた。 やりたいこと SEOのため、Reactでserver-side renderingをしたい JSコードをES6で記述したい 既存のCoffeeScriptのコードも共存させたい（後ほど書き換える予定） npmやgulpといったモダンな環境でアセット管理をしたい browserifyを使いたい Sprocketsが実現している機能は維持したい そもそもSprocketsは何をしているか 周知のことでしょうが念のためおさらい。 ファイル毎の依存関係の管理 application.jsなどのマニュフェストファイルがやってること altJSのコンパイル アセットのminify アセットの連結 アセットファイル名にMD5フィンガープリントを挿入 Sprocketsの問題点
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
BucketList App: Getting the Data (part 1) | appendTo
An Intro To Using npm and ES6 Modules for Front End Development
From ES5 to ES6 (ES2015) and ES2016
fixingGetStats
ECMAScript 6 Tutorial