mammoth-art-6111
02/18/2022, 4:57 PMlittle-cartoon-10569
02/20/2022, 6:58 PMpromise()
method in outputs, which I call in every assertion. Hopefully jest also supports promises like this?mammoth-art-6111
02/22/2022, 3:56 PMpromise()
method?little-cartoon-10569
02/22/2022, 9:45 PMdeclare module "@pulumi/pulumi" {
export interface OutputInstance<T> {
promise(withUnknowns?: boolean): Promise<T>;
}
}
mammoth-art-6111
02/22/2022, 9:54 PMlittle-cartoon-10569
02/22/2022, 9:56 PMmammoth-art-6111
02/22/2022, 10:19 PMlittle-cartoon-10569
02/22/2022, 10:20 PMmammoth-art-6111
02/22/2022, 10:24 PMlittle-cartoon-10569
02/22/2022, 10:24 PMmammoth-art-6111
02/22/2022, 10:24 PMlittle-cartoon-10569
02/22/2022, 10:26 PMpulumi up
, which doesn't happen during npm run test
...mammoth-art-6111
02/22/2022, 10:37 PMlittle-cartoon-10569
02/22/2022, 10:40 PMeven if resolving Input<T>/Output<T>?This can be variable, but since there are no real dependencies to wait on, all awaiting should resolve very, very quickly. There's always an overhead with promises in Node, which is why we can't reasonably expect sub-millisecond tests, but sub-10ms tests are very achieveable.
mammoth-art-6111
02/22/2022, 10:44 PMnock
and blocked all http requests, nothing is going out as far as I can tellisolatedModules
to true, which removes a lot of type-checking power but I guess you can get that via CI linter checkslittle-cartoon-10569
02/23/2022, 7:55 PMmammoth-art-6111
03/16/2022, 6:21 PMtsconfig-paths
it doesn't seem to work appropriately, i'm wondering if it's because Pulumi plays with env vars on the process, particularly process.env.TS_NODE_PROJECT