maxmustermann/pulumi
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
pulumi/examples/dynamic-provider/multiple-turns/package.json

17 lines
348 B
JSON
Raw Normal View History

Do not disconnect from the engine prematurely. The `nodejs` language support is implemented as two programs: one that manages the initial connection to the engine and provides the language serivce itself, and another that the language service invokes in order to run a `nodejs` Pulumi program. The latter is responsible for running the user's program and communicating its resource requests to the engine. Currently, `run` effectively assumes that the user's program will run synchronously from start to finish, and will disconnect from the engine once the user's program has completed. This assumption breaks if the user's program requires multiple turns of the event loop to finish its root resource requests. For example, the following program would fail to create its second resource because the engine will be disconnected once it reaches its `await`: ``` (async () => { let a = new Resource(); await somePromise(); let = new Resource(); })(); ``` These changes fix this issue by disconnecting from the engine during process shutdown rather than after the user's program has finished its first turn through the event loop.
2017-10-26 20:30:25 +02:00
{
"name": "minimal",
Add license fields to package.json. (#1656)
2018-07-25 01:10:13 +02:00
"license": "Apache-2.0",
Do not disconnect from the engine prematurely. The `nodejs` language support is implemented as two programs: one that manages the initial connection to the engine and provides the language serivce itself, and another that the language service invokes in order to run a `nodejs` Pulumi program. The latter is responsible for running the user's program and communicating its resource requests to the engine. Currently, `run` effectively assumes that the user's program will run synchronously from start to finish, and will disconnect from the engine once the user's program has completed. This assumption breaks if the user's program requires multiple turns of the event loop to finish its root resource requests. For example, the following program would fail to create its second resource because the engine will be disconnected once it reaches its `await`: ``` (async () => { let a = new Resource(); await somePromise(); let = new Resource(); })(); ``` These changes fix this issue by disconnecting from the engine during process shutdown rather than after the user's program has finished its first turn through the event loop.
2017-10-26 20:30:25 +02:00
"devDependencies": {
Run yarn upgrade and commit all resulting lockfiles This also adds lock files for some of our tests which we previously did not commit.
2018-01-30 00:42:24 +01:00
"@types/minimist": "^1.2.0",
"@types/node": "^8.0.25",
Upgrade Node.js SDK to TypeScript 3.0 (#1669) Per pulumi/pulumi#1668. No code changes required, just package.json and lockfile updates.
2018-07-31 08:19:28 +02:00
"typescript": "^3.0.0"
Do not disconnect from the engine prematurely. The `nodejs` language support is implemented as two programs: one that manages the initial connection to the engine and provides the language serivce itself, and another that the language service invokes in order to run a `nodejs` Pulumi program. The latter is responsible for running the user's program and communicating its resource requests to the engine. Currently, `run` effectively assumes that the user's program will run synchronously from start to finish, and will disconnect from the engine once the user's program has completed. This assumption breaks if the user's program requires multiple turns of the event loop to finish its root resource requests. For example, the following program would fail to create its second resource because the engine will be disconnected once it reaches its `await`: ``` (async () => { let a = new Resource(); await somePromise(); let = new Resource(); })(); ``` These changes fix this issue by disconnecting from the engine during process shutdown rather than after the user's program has finished its first turn through the event loop.
2017-10-26 20:30:25 +02:00
},
Run yarn upgrade and commit all resulting lockfiles This also adds lock files for some of our tests which we previously did not commit.
2018-01-30 00:42:24 +01:00
"dependencies": {
"assert": "^1.4.1",
"sleep-promise": "^2.0.0"
Rename pulumi package to @pulumi/pulumi (#917) In order to begin publishing our core SDK package to NPM, we will need it to be underneath the @pulumi scope so that it may remain private. Eventually, we can alias pulumi back to it. This is part of pulumi/pulumi#915.
2018-02-12 22:13:13 +01:00
},
"peerDependencies": {
"@pulumi/pulumi": "latest"
Run yarn upgrade and commit all resulting lockfiles This also adds lock files for some of our tests which we previously did not commit.
2018-01-30 00:42:24 +01:00
}
Do not disconnect from the engine prematurely. The `nodejs` language support is implemented as two programs: one that manages the initial connection to the engine and provides the language serivce itself, and another that the language service invokes in order to run a `nodejs` Pulumi program. The latter is responsible for running the user's program and communicating its resource requests to the engine. Currently, `run` effectively assumes that the user's program will run synchronously from start to finish, and will disconnect from the engine once the user's program has completed. This assumption breaks if the user's program requires multiple turns of the event loop to finish its root resource requests. For example, the following program would fail to create its second resource because the engine will be disconnected once it reaches its `await`: ``` (async () => { let a = new Resource(); await somePromise(); let = new Resource(); })(); ``` These changes fix this issue by disconnecting from the engine during process shutdown rather than after the user's program has finished its first turn through the event loop.
2017-10-26 20:30:25 +02:00
}
Reference in a new issue Copy permalink