pulumi/sdk/nodejs/runtime
Pat Gavlin 56db742627 Restore back- and forwards-compatibility in NodeJS
Continue to capture the statically-known set of dependencies (if any) in
Output.resources, and capture the dynamically-known set of dependencies
in Output.__asyncResources. This retains signature compatibility with
older versions. The behavior is as follows:
- If a newer Output instance is serialized by an older @pulumi/pulumi,
  dynamic dependencies will not be reported to the engine. This is
  consistent with the older behavior.
- If an older Output instance is serialized by a newer @pulumi/pulumi,
  its static dependencies will be reported to the engine. This is
  consistent with the older behavior.
- If a new Output instance is serialized by a new @pulumi/pulumi, its
  static and dynamic dependencies will be reported to the engine. This
  is new behavior.

Tests will come shortly.
2018-12-13 11:12:43 -08:00
..
closure Restore back- and forwards-compatibility in NodeJS 2018-12-13 11:12:43 -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 make the context-param non-optional for debuggable promises. (#2242) 2018-11-24 18:57:17 -08:00
resource.ts Restore back- and forwards-compatibility in NodeJS 2018-12-13 11:12:43 -08:00
rpc.ts Restore back- and forwards-compatibility in NodeJS 2018-12-13 11:12:43 -08:00
settings.ts make the context-param non-optional for debuggable promises. (#2242) 2018-11-24 18:57:17 -08:00
stack.ts Move management of root resource state to engine (#1944) 2018-09-18 11:47:34 -07:00