JavaScript naming conflicts: How existing code can force proposed features to be renamed
JavaScript naming conflicts: How existing code can force proposed features to be renamed Sometimes the name of a proposed feature (a method, a global variable, etc.) clashes with existing code and has to be changed. This blog post explains how that can happen and lists features that were renamed. Evolving JavaScript: Don’t break the web! # One core principle for evolving JavaScript is to not “bre
❌(REVERTED): Add text to MIT License banning ICE collaborators by jamiebuilds · Pull Request #1616 · lerna/lerna
I have already spoken to @kittens and @evocateur about this privately, but I do need @kittens to give us permission to make this change. Explanation Over the last year I've been really disturbed to see what ICE has done to American immigrants, to an extreme with what has happened to children. The other day I saw this video from the ACLU about a toddler who after being separated from his family for
1.0 · Issue #2473 · denoland/deno
Update April 15, 2020: Still go for May 13. Update March 6, 2020: There's a difficult balance to be had between trying to get it right and shipping a usable product. The repository continues to see rapid development and we have yet to make substantial progress on the major missing feature: dev tool support. Therefore we are bumping the release date yet again. However instead of blindly estimating
dayjs set month error · Issue #399 · iamkun/dayjs
console.log('test dayjs()'); console.log(dayjs().set('month', 0).month(), 0); console.log(dayjs().set('month', 1).month(), 1); // test not pass console.log(dayjs().set('month', 2).month(), 2); console.log(dayjs().set('month', 3).month(), 3); // test not pass console.log(dayjs().set('month', 4).month(), 4); console.log(dayjs().set('month', 5).month(), 5); // test not pass console.log(dayjs().set('m
Prettier 2.0 (old) · Issue #3503 · prettier/prettier
Note added by @j-f1: This is NOT the current plan for Prettier v2.0. We’ve significantly scaled back our plans for what Prettier 2.0 will do, allowing us to get a less-controversial release out sooner: #6888 I've been thinking a bit about what we would do if (don't create a milestone just yet 😉) we were to do a Prettier 2.0 release with some API/CLI breaking changes. No significant changes to cod
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
[Tracking]: Rspack v1.0 · Issue #6689 · web-infra-dev/rspack
"inconvenient" stack overflow when using spread operator - changing stack size does not work · Issue #16870 · nodejs/node
Default constructor for Promise statics · Issue #544 · tc39/ecma262
Poor URLPattern performance · Issue #19861 · denoland/deno
TAG Review Request: queueMicrotask · Issue #294 · w3ctag/design-reviews
Array.from doesn't work with some iterables · Issue #359 · prototypejs/prototype
perf: replace startsWith with === by sun0day · Pull Request #12531 · vitejs/vite
`__esModule` flag · Issue #86 · esnext/es6-module-transpiler
Fix `Symbol` compatibility detection under Terser by laverdet · Pull Request #1242 · zloirock/core-js
Is this project still ongoing? · Issue #2975 · lerna/lerna
[V8] Array.prototype.splice ~100x slower in V3 with symbol polyfill · Issue #677 · zloirock/core-js
Non-async source map. · Issue #331 · mozilla/source-map
tc39-notes/mar-20.md at master · rwaldron/tc39-notes · GitHub
JS Source Maps support by DeMoorJasper · Pull Request #506 · parcel-bundler/parcel
Add support for extending builtins by nicolo-ribaudo · Pull Request #7020 · babel/babel
