JavaScript の Module Fragments について
現在 TC39 の 3 月のミーティングのアジェンダが GitHub にて公開されている(Link)。 それによると、Module Frangments という新しいプロポーザルが@littledan氏によって提案される予定だ。 この記事では、現在の Module Frangments の概要とモチベーション、構文について解説する。もしさらなる詳細に興味がある場合は https://github.com/littledan/proposal-module-fragments を読んでほしい。 また、Module Fragments は現在 Stage 0 の提案であり、今後仕様が大きく変わっていくことが予想されるのでその点には注意してほしい。 概要 Module Fragments はインラインで JavaScript のモジュールを定義するための構文を導入する提案である。詳細は後述するが
【翻訳】Date and Times in JavaScript - from scratch
この記事は littledan から依頼を受けて、翻訳しています。広く Date and Times の JS プロポーザルについて意見がほしいとのことです。 意見は以下の場所にポストできます。 docs.google.com 原文: blogs.igalia.com tl;dr: Temporal のプロポーザルについてフィードバックを求めています。 Polyfill を試したら、サーベイの回答を送ってください、ただしまだ本番環境では使わないでもらいたいです。 JavaScript の Date クラスは壊れています、しかし Breaking the Web を起こさずに修正する方法はありません。風のうわさでは、 Date クラスは 10 日で作られた JS Engine のhackに含まれたもので、 java.util.Date に基づいたものと言われています。しかも java.uti
GitHub - Agoric/SES: MOVED to @agoric/ses-shim. SES (Secure EcmaScript) is a secure runtime for running third-party code safely
This repository contains the code for "Old SES": the one whose default export is a single object named SES, which has a property named SES.makeSESRootRealm(). This code was used to make all NPM releases of the SES package up through the '0.6.x' series. Modern SES development is now happening in the SES-shim repository. This "New SES" has a named export named lockdown(), which introduces the Compar
GitHub - Agoric/realms-shim: Spec-compliant shim for Realms TC39 Proposal
This repository contains a legacy shim implementation of an outdated Realm API Proposal. The Realms proposal has been superceded by the ShadowRealm Proposal. This shim does not implement ShadowRealm, which (as of this writing) is a proposal at Stage 3 of the TC39 standardization process, so common JS engines should have support soon. We do not recommend the use of this shim or the original Realms
Weak references and finalizers · V8
Show navigation Generally, references to objects are strongly held in JavaScript, meaning that as long you have a reference to the object, it won’t be garbage-collected. const ref = { x: 42, y: 51 }; // As long as you have access to `ref` (or any other reference to the // same object), the object won’t be garbage-collected.Currently, WeakMaps and WeakSets are the only way to kind-of-weakly referen
GitHub - WICG/scheduling-apis: APIs for scheduling and controlling prioritized tasks.
This document outlines the motivation for working on various scheduling APIs1, discusses some of the problems that apps and userspace schedulers face when writing scheduling code, and links to various proposals we are working on in this space. (1The scope of this work was previously restricted to main-thread scheduling, and while main-thread scheduling remains the primary focus, the repository and
SmooshGate FAQ | Blog | Chrome for Developers
What the smoosh happened?! A proposal for a JavaScript language feature called Array.prototype.flatten turns out to be Web-incompatible. Shipping the feature in Firefox Nightly caused at least one popular website to break. Given that the problematic code is part of the widespread MooTools library, it’s likely that many more websites are affected. (Although MooTools is not commonly used for new web
ECMAScript proposal updates at 2018-01
The changes of proposal’s status @ 62nd meeting of Ecma TC39 New Proposals Proposal Stage
GitHub - mikewest/tc39-proposal-literals: Literals could be different than non-literals.
HTML's DOM offers a number of mechanisms to turn arbitrary strings into markup (.innerHTML = ...) or code (scriptEl.innerText = ..., el.onclick = ..., etc). Each of these mechanisms can serve as an XSS sink, giving an attacker the ability to feed code into a context that wasn't expecting it, leading to a class of DOM-based XSS attacks that we'd very much like to avoid. One way of addressing this i
Finally the Promise.prototype.finally() is available
Finally the Promise.prototype.finally() is available Serg Hospodarets Blog Since the Promises were added in JavaScript, one of the biggest concerns was the absence of an ability to easily apply some code after the Promise is fulfilled (after both success and reject actions). There are many examples of such a need: showing a loader when the request to the server is in flight or even a simpler case-
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Intent to Prototype: App history API
GitHub - slightlyoff/history_api: Some ideas for to improve history state on the web
JavaScript Promise combinators: `.all()`, `.race()`, `.allSettled()`
GitHub - tc39/proposal-regexp-match-indices: ECMAScript RegExp Match Indices
https://github.com/sveltejs/rfcs/blob/master/text/0003-reactive-declarations.md
GitHub - WICG/js-self-profiling: Proposal for a programmable JS profiling API for collecting JS profiles from real end-user environments
GitHub - WICG/virtual-scroller
GitHub - conradreuter/cancellationtoken: A composable token for cancelling asynchronous operations.
GitHub - tc39/proposal-top-level-await: top-level `await` proposal for ECMAScript (stage 4)
JavaScript with 5 Characters? +[]|>