Breaking Require Node.js 20 (#2313) a004263 Why not target the oldest active Node.js LTS, which is Node.js 18? I usually strictly follow this convention in my packages. However, this package is the exception because the HTTP part of Node.js is consistently buggy, and I don't have time to work around issues in older Node.js releases. I you need to still support Node.js 18, I suggest staying on Got
Breaking Require Node.js 12.20 (#478) 7707880 This package is now pure ESM. Please read this. Moved from a default export to named exports. require('execa') → import {execa} from 'execa' require('execa').sync → import {execaSync} from 'execa' require('execa').command → import {execaCommand} from 'execa' require('execa').commandSync → import {execaCommandSync} from 'execa' require('execa').node → i
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
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く