We had a discussion in TC39 this week about how to think about the JS module system's default export feature. It turns out one of the ways people explain this feature is as a shorthand for an export with the name default. For example: import LoadingSpinner from 'loading-spinner'; is equivalent to: import { default as LoadingSpinner } from 'loading-spinner'; This is technically accurate information
This week's meeting has a few different Promise-related spec changes. Promise.try: async function as a Library One of the goals of Promise APIs is that exceptions that happen while processing the request become Promise rejections, rather than bubbling up to the top level (e.g. window.onerror). This is true regardless of whether the error happened right away, or later on as the processing continues
This week, I asked on Twitter what TC39-related topics, people wanted me to talk about on this blog. Julia Evans (@b0rk) threw a bunch of questions at me, and I'll try to answer them one at a time. @wycats who is in the meeting? do you have to implement the future of JavaScript before you decide on it? — Julia Evans (@b0rk) November 30, 2016 Do you have to implement the future of JavaScript before
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く