Tracing certain system polyfills can lead to infinite loops or incorrect results (e.g. process.cwd)

[Domiii]

Problem: graceful-js/polyfills.js patches process.pwd(), but pwd is called internally by node in several different situations. As a result, code gets traced while runtime is doing its own thing.

• Ideal solution: don't trace any code while @dbux/runtime code is running.
  • NOTE: only guarding read access is helpful but not sufficient.
  • One of the bugs we had was related to Node@14 executing an instrumented polyfill every time a stacktrace was generated.
• hackfix: always disable tracing of graceful-js (for now)
  • Another possible hackfix: disable tracing of process.cwd somehow
  • wrap with tracesDisabled via CallbackPatcher

Related

• require node@16 (reduce monkey-patch-induced infinite loops) #593