little-cartoon-10569
06/08/2020, 11:17 PMerror: Error: Error reading file '/pulumi/projects/main/pulumi/projects/autostop/package.json' when computing package dependencies. Error: ENOENT: no such file or directory, open '/pulumi/projects/main/pulumi/projects/autostop/package.json'
at readFile (/pulumi/projects/node_modules/@pulumi/pulumi/runtime/closure/codePaths.js:167:19)
at computeDependenciesDirectlyFromPackageFile (/pulumi/projects/node_modules/@pulumi/pulumi/runtime/closure/codePaths.js:150:22)
at /pulumi/projects/node_modules/@pulumi/pulumi/runtime/closure/codePaths.js:115:36
at /pulumi/projects/node_modules/read-package-tree/rpt.js:162:20
billowy-army-68599
06/08/2020, 11:20 PMpackage.json
? seems like that file isn't therelittle-cartoon-10569
06/08/2020, 11:20 PMnode_modules
directory..
only for the file, as opposed to the normal behaviour which is to ascend the directory tree until it is found?EventRuleEventSubscription
and has TypeScript code that gets converted to an AWS Lambda.. the other project doesn't...codePaths.js
is replicating the package.json-finding behaviour, but missing the rule that says "look here _or in parent directories_"....codePaths.js
and the logic is only to look in the current directory and nowhere else.billowy-army-68599
06/08/2020, 11:37 PMlittle-cartoon-10569
06/08/2020, 11:45 PMrequire('path')
then path.resolve()
for any parameter that's passed to read-path-json
. But Pulumi is just passing .
to the same function.path
module but I can't see it in npm's own package.json, and I don't know enough about JS to find it...path.resolve()
, that's not the issue... still looking...