Roey Berman

This makes sense. We need to figure out how to make workflow bundling more extensible. If you can get this to work, we'll make sure to add support in the...

The Worker (and bundler) accepts `workflowsPath` because workflows run in a [vm](https://nodejs.org/api/vm.html) instead of in the same JS environment as the worker and activities. We've used "exporting" as the way...

That's a great suggestion @mjameswh. I'd definitely accept a default function export.

Apart from that [one issue](https://github.com/temporalio/sdk-typescript/issues/1051) where we weren’t maintaining the name in the type, we haven’t had any complaints about deficiencies in the type definitions. I fear over testing the...

Seems like fairly low ROI. > That one and the one that Dan just exposed. That issue was closed, it was working as expected. So again, it's just a single...

I don't think we want confirmation for termination / cancellation of a single workflow, it's reversible. I'm okay with adding it to delete.

Does PHP client support lazy and eager creation? Does it call `getSystemInfo` on connection? Is the gRPC health service exposed via the client? We have all of that in the...

In other languages we have a lazy method to create a connection (client) that doesn't make any calls to the server, and an eager connection method that fails if `getSystemInfo`...

Reopening this with some more context so we keep this tracked. Take for example the activity state machine. In Core we keep the input around for the lifetime of the...

We discovered that we don't drop the state machines at all today, we should consider fixing that too, not just dropping the payloads.