Mark S. Miller
Mark S. Miller
> Any chance you have NODE_OPTIONS set? We don't. I grepped and the only mention of `NODE_OPTIONS` anywhere in our code is in an `esm-*.patch` file: https://github.com/Agoric/agoric-sdk/blob/master/patches/esm%2B3.2.25.patch
See https://github.com/microsoft/TypeScript/issues/43463 https://github.com/microsoft/TypeScript/issues/43450 https://github.com/mrkmg/node-external-editor/issues/25
Re https://github.com/endojs/endo/issues/576#issuecomment-809131839 and https://github.com/endojs/endo/issues/612 We need to file a bug against https://github.com/benjamn/wryware/blob/569d7a6294b77aa9e71d7c7709344aca7cbb75a1/packages/context/src/slot.ts#L126-L135 .
Re https://github.com/vega/vega/pull/3109#issuecomment-792590332 we need to file a bug against rollup for the way it generates the `exports` object by assignment.
I have now enhanced it to be compatible with users of the old interface. The adaptation was ugly, but worth it avoid a more painful upgrade dance. It is now...
Do you have a reason to turn on `consoleTaming: 'unsafe'`? Without it, do you see error stacks?
> I'm guessing the way to fix this would be to replace the `Promise.resolve(result).catch(..)` with an `E.when(result).catch(..)`, but I'm not positive. except that we need to avoid the infinite regress...