サクサク読めて、アプリ限定の機能も多数！
トップへ戻る
デスク環境を整える
github.com/sindresorhus
You 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
At the end of April, Node.js 10 goes out of LTS, which means I can target Node.js 12 in my packages. Node.js 12 has full ESM support! Required reading: https://nodejs.org/api/esm.html I plan to migrate most of my (1K+) packages to ESM within 2021. At the start of April, I will begin with some less popular packages, just to test the waters. I will use "type": "module" in package.json and not .mjs.
I intend to stop using null in my code, in favor of undefined. There are many reasons for doing so. Feedback wanted Tweet: https://twitter.com/sindresorhus/status/1114894287387258886 Background http://2ality.com/2013/05/history-undefined.html Reasons From experience, most developers use null and undefined inconsistently and interchangeably, and few know when to use which. Supporting both null and
You 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.
import onChange from 'on-change'; const object = { foo: false, a: { b: [ { c: false } ] } }; let index = 0; const watchedObject = onChange(object, function (path, value, previousValue, applyData) { console.log('Object changed:', ++index); console.log('this:', this); console.log('path:', path); console.log('value:', value); console.log('previousValue:', previousValue); console.log('applyData:', app
次のページ
このページを最初にブックマークしてみませんか？
『sindresorhus - Overview』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
