Thanks to Sindre Sorhus, ehmicky, GMartigny, BendingBender, tomsotte, Malik Ammar Faisal, zokker13, stroncium, Satya Rohith, Brad Lemley, coreyfarrell, Brandon Smith, Thai Pangsakulyanont and Pedro Augusto de Paula Barbosa, the following features are now available:
There’s something wrong with your code. At least, this is what the following warning seems to indicate:
All the tests are passing but this
ExperimentalWarning leaves you unsettled. What baffles you is that
queueMicrotask() is not directly used anywhere.
Warnings are harder to debug because they are not part of a program’s control flow. Instead, Node.js emits them on the global
process. This is also the case for uncaught exceptions and mishandled promises.
Ignoring those process errors is not an option as they usually point to a bug. However, the way they are reported by Node.js is not developer-friendly.
The issue above would be simple to solve if stack traces had been…