No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Code:
```   error: 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```

In case it's relevant: I'm running Pulumi from <@UCWG26BH7>'s node-specific Pulumi image.

did you forget to check in your `package.json` ? seems like that file isn't there

It's not there, deliberately. It's in _/pulumi/projects_, beside the `node_modules` directory.

I can run Pulumi from the other project, and run Mocha from the test directories, and they all find the correct package.json. Just this one project is set up differently somehow, and I can't see the difference.. no idea what to look for...

What influences Pulumi to look in `.` only for the file, as opposed to the normal behaviour which is to ascend the directory tree until it is found?

Oh wait I see a potentially-relevant difference.. this module is using `EventRuleEventSubscription` and has TypeScript code that gets converted to an AWS Lambda.. the other project doesn't...

Maybe `codePaths.js` is replicating the package.json-finding behaviour, but missing the rule that says "look here _or in parent directories_"....

Yep that's it. It's not using npm to load the file, it's doing it on line 115 of `codePaths.js` and the logic is only to look in the current directory and nowhere else.

<@U012UJTT55M> you should be able to pass -C to the cmd to have it check a different path 

There's no command? This seems to be happening when Pulumi is compiling my inline handler parameter to aws.cloudwatch.onSchedule into a Lambda.

I'm looking in the npm code, it's using `require('path')` then `path.resolve()` for any parameter that's passed to `read-path-json`. But Pulumi is just passing `.` to the same function.

I'm trying to find the `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...

If I can find the solution I can raise an issue.

Found `path.resolve()`, that's not the issue... still looking...

Issue created at <https://github.com/pulumi/pulumi/issues/4780>