https://pulumi.com logo
#typescript
Title
# typescript
l

little-cartoon-10569

10/20/2020, 9:53 PM
I'm using a monorepo with several Pulumi projects, each in their own directory. They share a single _node___modues_ and package.json. One of the projects deploys lambdas, and somehow back in the mists of time, it got its own package.json, presumably for building the lambda code. I'm now moving the resources into another project, and on
pulumi up
I'm getting ENOENT errors about a missing package.json. I could probably copy the defunct project's package.json, but I'd rather build a new one. How do I force npm or Pulumi to build a new package.json for use by the lambda-deploying code?
Using a symbolic link to the top-level package.json works, but is it the right thing to do?
8 Views