CyrusNajmabadi d4aa5fe20d Switch to 'console.log' for our hang warning. Add warning to synchronous StackReference calls. (#3456) ... Codepaths which could result in a hang will print a message to the console indicating the problem, along with a link to documentation on how to restructure code to best address it. `StackReference.getOutputSync` and `requireOutputSync` have been deprecated as they may cause hangs on some combinations of Node and certain OS platforms. `StackReference.getOutput` and `requireOutput` should be used instead.		2019-11-19 12:51:14 -08:00
..
closure	Perform our closure tree-shaking when the code contains element accesses, not just property accesses (#3295)	2019-10-02 23:34:09 -07:00
asyncIterableUtil.ts	`StreamInvoke` should return `AsyncIterable` that completes	2019-11-12 13:51:19 -08:00
config.ts	Do not lazy initialize config or settings	2018-08-06 15:53:38 -07:00
debuggable.ts	make the context-param non-optional for debuggable promises. (#2242)	2018-11-24 18:57:17 -08:00
index.ts	Actually export type. (#1971)	2018-09-21 11:58:58 -07:00
invoke.ts	Switch to 'console.log' for our hang warning. Add warning to synchronous StackReference calls. (#3456)	2019-11-19 12:51:14 -08:00
resource.ts	Propagate inputs to outputs during preview. (#3327)	2019-11-11 12:09:34 -08:00
rpc.ts	Propagate inputs to outputs during preview. (#3327)	2019-11-11 12:09:34 -08:00
settings.ts	New approach to move us to using `deasync` as little as possible (and with as little impact to users as possible). (#3325)	2019-10-14 22:08:06 -07:00
stack.ts	Omit unknowns in resources in stack outputs during preview. (#3427)	2019-10-30 11:36:03 -07:00